Jump to content











Photo
- - - - -

HDD Regenerator: Bad command error


  • Please log in to reply
7 replies to this topic

#1 Alexander Ceed

Alexander Ceed

    Frequent Member

  • Advanced user
  • 185 posts

Posted 02 August 2016 - 11:29 AM

I burned an HDD Regenerator to a DVD today and it gives me the error: 

Starting HDD Regenerator...
Bad command or filename

This is also given in grub4dos, for both iso and floppy image (ima). Entry used in grub4dos:

title HDD Regenerator 1.71
find --set-root /data_disk
map --mem /iso/HDDREG171.iso (hd32)
map --hook
chainloader (hd32)

title HDD Regenerator 1.71
find --set-root /boot_disk
map --mem /ima/HDDREG171.ima (fd0)
map --hook
root (fd0)
chainloader (fd0)+1
rootnoverify (fd0)

It works however if it is burned to a CD. And only to a CD. However, the iso and ima images are made from that CD. I don't understand why this happens. 

It only happens with 1.61 and 1.71. 

1.51 works fine.

 

Please help.

Thank you!



#2 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13334 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 02 August 2016 - 12:01 PM

I don't understand why this happens. 

It only happens with 1.61 and 1.71. 

1.51 works fine.

This is then likely an issue with those versions of the program, ask their support:

http://www.dposoft.net/feedback.php

 

:duff:

Wonko
 



#3 Agent47

Agent47

    Frequent Member

  • Advanced user
  • 164 posts
  •  
    India

Posted 02 August 2016 - 02:16 PM

Hi

 

Try using "memdisk" from ISOLINUX package. 

 

http://www.syslinux....p?title=MEMDISK

 

I had some issues booting a number of DOS images using Grub4dos "map" command but all fixed when i switched to the "memdisk" method.

 

Here is the code i used to load "HDD regen 2011" which is newer than 1.71.

title HDD Regenerator
find --set-root /Boot/DOS/hddregen.img
kernel /Boot/DOS/memdisk
initrd /Boot/DOS/hddregen.img



#4 Wonko the Insane

Wonko the Insane

    Frequent Member

  • Advanced user
  • 458 posts
  • Location:The Inside of the Asylum (gate is wide open)
  • Interests:Oh, so you hate me too? Well, join the club! There are weekly meetings at the corner of Fuck You St. and Kiss My Ass Blvd.
  •  
    United States

Posted 02 August 2016 - 07:21 PM

This is meant as an off-topic comment, but softwares like HDD Regenerator and SpinRite seem a bit scammy and like snake oil, they haven't been proven to work. I've tried both and feel like they didn't really help. They may even cause more harm than good, making a drive's condition worse. In the end nothing will save a drive if it is failing hardware-wise, you're much better off buying new ones. It's my understanding that drive damage can be due to either software errors (which HDD Regenerator/SpinRite may or may not be able to fix) or hardware errors (like damaged platters, bad sectors), or both.



#5 Alexander Ceed

Alexander Ceed

    Frequent Member

  • Advanced user
  • 185 posts

Posted 03 August 2016 - 08:13 AM

I agree with you Anon, 100%. But I've had some drives that were unable to read some sectors but they were not bad, they were "stuck", meaning not bad or good just something in between. This made windows load very slow and caused programs to crash or freeze. Most of time, I managed to solve these issues buy just writing extensively on the drive for several hours. Which I why I sometimes need this program: that's exactly what it does. Spins up the drive, forces it to read and write, again and again.

I never used this for data recovery as I'm no fool.

 

 

 

Also, as a solution, apparently the the drives work fine but only on some computers due to himem.sys error (ramdisk). I tested the original HDDREG 1.61 and 1.71 on laptops with 8GB ram and the RAMDISK driver could not be loaded. Then I replaced CONFIG.SYS from the floppies with the above and it worked fine:  

break=on
device=himem.sys /testmem:off /M:1
files=10
buffers=10
dos=high,umb
stacks=9,256
devicehigh=ramdrive.sys /E 4096
lastdrive=z

@Wonko I should've called support but as we all know, support is always late in reply and I did it way faster.

 

Thank you guys once again.



#6 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13334 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 03 August 2016 - 10:34 AM

Good :), cannot say if it applies to the specific program tool, but when it comes to DOS ramdisks I have traditionally been very happy to use either Frack Uberto's one or SRDISK, instead of the original MS one.
Though I believe that issues with MS-DOS one are not - strangely enough - MS's fault, but rather due to some changes that were made to chipsets and arrangement/indexing of RAM on some newer motherboards.

:duff:
Wonko

#7 Alexander Ceed

Alexander Ceed

    Frequent Member

  • Advanced user
  • 185 posts

Posted 03 August 2016 - 10:45 AM

One last question since we're on the subject: are there any updated MS-DOS disks (that uses new ramdisk like xmsdsk)? 

I know FreeDOS exists but I find MS-DOS more stable.



#8 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13334 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 03 August 2016 - 11:08 AM

One last question since we're on the subject: are there any updated MS-DOS disks (that uses new ramdisk like xmsdsk[/size])?

Well, you create one, what is the problem?
http://www.geocities...lk/index-2.html
http://www.geocities...ootdisk.htm#dos
http://www.geocities...mdrv/index.html

:duff:
Wonko




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users