Here is what ultimately determines the feasibility: is 'SHCDX33A" a file or
a directory? if a file, is it exe or com?
where is it to be found? where is it supposed to be loaded into? I say this
because the bugaboo always seems
to be that when you 'activate' the fdos from the 'c' drive being shared with
98, everything goes well except
the message: "no drives assigned SHCDX33A could not load!". Can SHCDX33A be
manually loaded into
place after the fact? Or even before the fact of executing the bat file that
does the trick? Here is an irony:
the neat little package "DOSUSB", which gives you flash drive from fdos,
(drive 'd') allows the cd to keep
working(bumping it to drive 'e'); this DOSUSB fails if you simply
"quick-fix" the cd situation by loading from
a boot floppy/cd , that is, boot from the floppy/cd, which has it's own cd
driver , then do auto or fd .bat; the
cd driver persists. But then the DOSUSB fails to assign a drive letter under
those circumstances. However,
when the fdos has drive 'c' all to it self, and can boot it's normal way,
you get the cd from fdos and can put
the USBDOS into the works. This is like a computer 'game', but in slow
motion. Anybody got the straight
dope on that SHCDX33A? kurt, <[EMAIL PROTECTED]>.
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Freedos-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-user
