missing hdderase.bat file?

[Victor Chew]

So for all you guys having the drive detection problem, could you please try IceCube's solution and let us know how it goes?

Basically, download http://ubcd.stopspazzing.com/downloads/ ... bcd.iso.gz to "c:\ubcd-extracted\ubcd\images". Then modify "c:\ubcd-extracted\ubcd\menus\hdd\wiping.cfg":

Code: Select all

LABEL -
MENU LABEL HDDErase V4.0
TEXT HELP
 Securely erases all data on ATA hard disk drives. It offers the option to run
 the drive internal secure erase command, security erase unit, based on the ATA
 specification by the T13 technical committee.
ENDTEXT
LINUX /boot/syslinux/memdisk
INITRD /ubcd/images/fdubcd.iso.gz
APPEND iso raw ubcdcmd=hdderase

Bolding the important part:

INITRD /ubcd/images/fdubcd.iso.gz
APPEND iso raw ubcdcmd=hdderase

Make the customized ISO or USB, then try launching HDDErase again.

Edit by Icecube: added bolded part

[Victor Chew]

@IsLNdbOi: There's a new build of eltorito.sys that IceCube suggests might resolve the missing CDROM drive problem.

If you have the time, could you please try it and let us know? Here's a build of fdubcd.img that includes the new eltorito.sys:

http://www.ultimatebootcd.com/misc/fdub ... z.20100615

Thanks!

[IsLNdbOi]

What do I do with that file? Do I simply copy it and overwrite an existing version of it in the UBCD ISO?

[Victor Chew]

@Anmorphic: Could you please try UBCD V5.1a1:

viewtopic.php?t=2661

Description:

This is the first alpha for UBCD V5.1 whose primary purpose is to solicit feedback.

The major structure change in this release is moving FreeDOS UBCD and DOS apps to an ISO image (\ubcd\images\fdubcd.iso.gz). The reason for this change is to allow FreeDOS-based apps to work even on systems where FreeDOS has problems recognizing/mounting the source CD or USB memory stick.

A new script has been created (\ubcd\tools\win32\mkfdubcd\mkfdubcd.cmd) that lets you create your own fdubcd.iso.gz after extracting it to a folder outside of the extracted UBCD folder hierarchy.

[ady]

@Victor,

He (Anmorphic) already resolved the problem, as he said:

Please ignore me, I must have removed necessary files...

So in that sense, it's all good with UBCD.

But, if someone would want to try UBCD51a1 to run DOS programs, it would be necessary for that user to resolve the fdubcd.ISO bug (instead the wrong fdubcd.IMG) before burning. For interested users, the relevant instructions to resolve the bug are also published in the UBCD51a1 announcement topic.