7 replies to this topic

[Uneitohr]

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!

[Wonko the Sane]

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

 

Wonko
 

[Agent47]

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

[Uneitohr]

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.

[Wonko the Sane]

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.


Wonko

[Uneitohr]

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.

[Wonko the Sane]

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


Wonko