home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!know!mips2!news.bbn.com!usc!sol.ctr.columbia.edu!vmsb.is.csupomona.edu!cvadrtbc
- From: cvadrtbc@vmsb.is.csupomona.edu (Srikanth Viswanathan)
- Newsgroups: comp.os.os2.misc
- Subject: Re: DOS VDM can't see new file in A:
- Message-ID: <29AUG199222302844@vmsb.is.csupomona.edu>
- Date: 30 Aug 92 06:30:00 GMT
- References: <1992Aug26.051615.2285@nuscc.nus.sg> <1992Aug26.053814.13068@news.columbia.edu> <27AUG199210410687@vmsa.is.csupomona.edu> <1992Aug27.200258.6246@njitgw.njit.edu>
- Sender: news@ctr.columbia.edu (The Daily Lose)
- Organization: California Polytechnic University, Pomona
- Lines: 18
- News-Software: VAX/VMS VNEWS 1.41
- X-Posted-From: vmsb.is.csupomona.edu
- X-Posted-Through: sol.ctr.columbia.edu
-
- >>
- >>Yeah, just change the DOS_STARUP_DRIVE in the Settings to B: instead of
- >>A:.
- >
- >That doesn't work. At least it doesn't on my computer.
- >DOS_STARTUP_DRIVE must either be A:, or a path to an image file on the
- >hard disk.
- >
- >Note that it's simple to make an image file from a disk in drive B:.
-
- Yeah, my mistake! That's what I was thinking. I used VMDISK B: c:image.fil
- and used STARTD to run the image.fil, so I assumed that you should be able
- to boot from drive B. You know what's weird? I just tried it right now,
- and it accesses drive B but goes to drive A (like it does when you run some
- utilities). Hmm. Nonetheless, thanks for pointing that out!
-
- Srikanth
- Clinton & OS/2 in '92!
-