Michael Devore schreef:

Okay, I fooled around with BOOT.ASM using NASM and got a workable boot sector for the flash drive if USB-ZIP is specified as boot device.

Basically the flash drive now boots up as a huge honking A: drive. Can't run USBASPI.SYS/DI1000DD.SYS in its CONFIG.SYS to remap the drive because everything gets terribly confused due to the drive letter changing while CONFIG.SYS is running. And then I have to manually input the COMMAND.COM location and parameters, plus go through a drive A: failed abort/retry/fail/ignore prompt a couple times. Which is too much trouble to get the flash drive off of A:.

But I can probably live with it booting up and living as A:. As long as nothing makes assumptions about how big that drive can be.

Michael,

config.sys can live without absolute paths (DEVIC=\DRIVERS\HIMEM.EXE),
and WinImage (www.winimage.com) can take diskette bootsector and transform them into bootsector for USB key, if I recall correctly.
if you need paths in autoexec.bat, you can use a variable automatically generated by FreeCOM (and 4DOS) called %_CWD%
('current working directory').


also
SHELL=COMMAND.COM /F /P /MSG might help.
A non-MS shell under MSDOS requires that you specify the location of the shell:
SHELL=A:\COMMAND.COM A:\ /F /P /MSG


I haven't tried my USB Key yet, but if I succeed, it will save me from using diskettes in the future.

Bernd


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/
_______________________________________________
Freedos-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Reply via email to