home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.os2.misc
- Path: sparky!uunet!mcsun!sunic!ugle.unit.no!lise.unit.no!hafting
- From: hafting@Lise.Unit.NO (Helge Hafting)
- Subject: Re: VDISK.SYS in one specific DOS Windows
- Message-ID: <1992Sep3.104421.23732@ugle.unit.no>
- Sender: news@ugle.unit.no (NetNews Administrator)
- Organization: Norwegian Institute of Technology
- References: <92246.095542BRYAN@wvnvm.wvnet.edu>
- Date: Thu, 3 Sep 92 10:44:21 GMT
- Lines: 25
-
- In article <92246.095542BRYAN@wvnvm.wvnet.edu>, Jerry Bryan <BRYAN@wvnvm.wvnet.edu> writes:
- > Some time ago there was a discussion about VDISK.SYS. I reported that
- > VDISK.SYS could be used in CONFIG.SYS, in which case the defined
- > virtual disk would be globally accessible to all OS/2 and DOS windows.
- > This does indeed work. I also reported that VDISK.SYS could be used
- > for just one DOS window, in which case the defined virtual disk would
- > be local to just that one DOS window. It was reported to me via private
- > mail that this does not work. The DOS window crashes.
- >
-
- VDISK is an os/2 device-driver, as far as I know.
- An os/2 driver is always loaded when os/2 boots, and is therefore accessible
- to all os/2, dos & windows programs.
- Only dos device drivers can be accessible to only one dos session.
- (ansi.sys is a dos-driver.)
- If you try to use an os/2 driver as a driver for dos, dos will try to use
- it as a dos driver, and this will probably crash the dos session.
- I cannot see why you want a virtual disk restricted to only one dos-session,
- but you might try a msdos virtual disk driver, such as ramdrive.sys .
- --
- | | ^ | | / ^ o
- |__| _ /| _ _ |__| _ /| /| | _ _
- | |/_| / | / \/_| | |/ | /-+-/-+- /| /|/ | / \
- | |\__/ |/\_/\_ | |\_|/ | \_/ |/ | |/\_/
- __/ / __/
-