home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!stanford.edu!rutgers!njitgw.njit.edu!hertz.njit.edu!dic5340
- From: dic5340@hertz.njit.edu (David Charlap)
- Newsgroups: comp.os.os2.misc
- Subject: Re: Whats needed to run E.EXE?
- Message-ID: <1992Aug19.203858.16715@njitgw.njit.edu>
- Date: 19 Aug 92 20:38:58 GMT
- References: <19AUG199208472481@cl2.cl.uh.edu>
- Sender: news@njit.edu
- Organization: New Jersey Institute of Technology, Newark, N.J.
- Lines: 22
- Nntp-Posting-Host: hertz.njit.edu
-
- In article <19AUG199208472481@cl2.cl.uh.edu> CSCI11BA@cl.uh.edu writes:
- >Greetings,
- >
- >I just made myself a bootable floppy with MAKEBOOT.CMD, and now I am
- >trying to figure out how to invoke the system editor (E.EXE)...
- >with no luck. It seems the more DLL's I point to in config.sys, the
- >more trouble I am getting myself into. Id like to be able to put
- >E.EXE on a floppy, and run it from there, just in case the HD crashes, etc.
- >
- >So, can anybody tell me what I need to stick on the floppy in order to
- >execute the system editor without the system telling me it cant find
- >'xxxx'.DLL???
-
- Not bloody likely. E.EXE is a PM application. PM is a huge slew of
- DLL's. There isn't enough room on two floppies to hold them, even if
- there was nothing else there.
-
- --
- |) David Charlap "I don't even represent myself
- /|_ dic5340@hertz.njit.edu sometimes so NJIT is right out!.
- ((|,)
- ~|~ Hi! I am a .signature virus, copy me into your .signature file.
-