NOD32 DOS on a Bootable USB Stick (or CD)

[Andaho]

I have NOD32DOS and it looks cool and easy to use, but I can't scan my harddrives when I boot up on my USB stick...

I've only just recently found out how to make a USB drive bootable, but I don't knowwhat to do to get it to load drivers or something for common hard drives, so it's useless... nod32dos can't scan the local hard drives!

What is it I needot put on my boot disk to allow me to scan the drives?

[directhex]

MS-DOS doesn't support any disk controllers which don't support the ancient IDE interfaces. tracking down MS-DOS drivers for your SATA controller is... well, good luck with that.

[Andaho]

but utility boot cds that run under dos don't seem to have a problem with it

[kidzer]

DOS != MS DOS though, there are a number of DOS-type OS' - CD's like UBCD will use a different DOS OS, that may have been more recentley updated with generic SATA drivers or similar - so that they can work with newed HD's.

[Andaho]

DOS != MS DOS though, there are a number of DOS-type OS' - CD's like UBCD will use a different DOS OS, that may have been more recentley updated with generic SATA drivers or similar - so that they can work with newed HD's.

well yeah, that's exactly what I'm after lol... surely there's a pack someone has made up for running off a CD or USB flash drive?

[peterb]

As part of the boot sequence (in fact at the end of POST) the bios jumps to an instruction at CHS adrress1 on the hard drive and loads the code in the first sector. This in turn calls additional code wihich may include loading specific drivers.

USB devices will have a similar boot process, so the boot loader has to be configured to load the appropriate drivers.

Since you are booting into DOS, you might be able to load the drivers that way (in the same way DOS could be configured to load CDROM drivers in the days when the bios didn't natively support them You would need to modify the config.sys and/or autoexec.bat files to do this.

[Andaho]

As part of the boot sequence (in fact at the end of POST) the bios jumps to an instruction at CHS adrress1 on the hard drive and loads the code in the first sector. This in turn calls additional code wihich may include loading specific drivers.

USB devices will have a similar boot process, so the boot loader has to be configured to load the appropriate drivers.

Since you are booting into DOS, you might be able to load the drivers that way (in the same way DOS could be configured to load CDROM drivers in the days when the bios didn't natively support them You would need to modify the config.sys and/or autoexec.bat files to do this.

Way too complicated... I want to make my USB stick usable in ANY PC to use as a virus scanner.

[peterb]

It would be - once you have created the boot sector and loaded the appropriate drivers on the USB stick so it is a self contained item. But it would only work on PCs that have a bios that can boot from a USB device of course.

You need to get a DOS manual to learn how to load the drivers (loadhigh a:drivername.xxx) is a command that rings bells with me, loads the driver into hi memory, that is memory above the first 640K (remember we are talking DOS here). IIRC, that goes into config.sys (of course the drive letter will be the appropraite one for the USB stick - B?). The final line in autoexec.bat would be the call to the application iself.