Hi!
Blair Campbell пишет:
INSTALL= commands are always executed AFTER the SHELL line because all
INSTALL does is call %SHELL% to execute the command
No. Kernel executes programs from INSTALL directly, without shell help.
---
Using Tom
INSTALL= commands are always executed AFTER the SHELL line because all
INSTALL does is call %SHELL% to execute the command
On 5/15/06, Lester Vedrox <[EMAIL PROTECTED]> wrote:
Molto grazia, Roberto. I forgot about this option and it works in
Config.sys:
INSTALL=C:\FDOS\BIN\SHSURDRV.EXE 8192K /V
LH C:\FDOS\BIN\CTMOUSE.EXE
Lester
> - Original Message -
> From: "Blair Campbell" <[EMAIL PROTECTED]>
> To: freedos-user@lists.sourceforge.net
> Subject: [Freedos-user] Re: Problems Loading SHSURDRV.EXE
> Date: Sun, 14 May 2006 15:14:59 -0700
>
>
> I
Molto grazia, Roberto. I forgot about this option and it works in
Config.sys:
INSTALL=C:\FDOS\BIN\SHSURDRV.EXE 8192K /V
I noticed that the sequence at which the commands are actually executed
(hit F8 at boot time) is different for TDSK.EXE and for SHSURDRV.EXE. It
looks like shsurdrv insis
Lester Vedrox schreef:
Both older ram disk drivers (tdsk.exe and xmsdsk.exe) were loaded from
Config.sys that's why I initially put shsurdrv there. The following works fine
but is it really the best way to load it?
- Autoexec.bat -
C:\FDOS\BIN\SHSURDRV.EXE 8192K /V /Q
SHCDX33A /D:?CDR
I didn't even know that shsurdrv could even be used in config.sys
On 5/14/06, Lester Vedrox <[EMAIL PROTECTED]> wrote:
I'm trying to use the new (Dec-2005) SHSURDRV.EXE from Jason Hood's
website to create a RAM drive:
http://www.geocities.com/jadoxa/
When used straight from the command line it
