Hi Bob.

09-Nov-03 09:39:01, Bob Lawrence wrote to Jasen Betts


 JB>> yeah, I see that string here too. (inside the execuutable)

 BL> Inside *which* executable? I looked in scandisk.exe, command.com,
 BL> io.sys and msdos.sys... nothing!

it's encrypted  (compressed actually)  Dos 6.22s Scandisk.exe

IIRC the compressed it with exepack and then pklite commercial, so you'll
need a 3rd party de-packer to extract it.


 JB>> scandisk a floppy on the new computer,

 BL> Did that... after I *booted* from a floppy.

 JB>> try it with the hard drive unplugged or disabled.

 BL> I don't understand. If I boot from a floppy there is no PATH. How
 BL> is the hard drive(s) involved? The problem has to be in the sytem
 BL> files or in scandisk itself... and since the old computer doesn't
 BL> mind when I boot from the *same* floppy, doesn't that mean it's in
 BL> the computer BIOS?

pretty much unless it's peeking at the hard disk on the sly.

 BL> I thought there must be an error in Win98, but Linux is even
 BL> slower to load files! Does it read the register first, or is it
 BL> somethign to do with the disk controller?

I'm not sure, Ive noticed that too, mainly on my old 486.

 It just sits there for a
 BL> few seconds the first time you load a new program, then it loads.
 BL> The next time (when it's already in RAM) it's pretty fast.

it may need to load the bit that knows how to load the program first....

 -=> Bye <=-

---