Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!uunet!mcsun!ukc!stc!mickb
From: mickb@tcom.stc.co.uk (Mick Brennan)
Newsgroups: comp.windows.ms
Subject: Help
Message-ID: <1991Apr24.121130.823@tcom.stc.co.uk>
Date: 24 Apr 91 12:11:30 GMT
Sender: news@tcom.stc.co.uk (USENET News System)
Organization: BNR Europe, New Southgate, London, N11 1HB
Lines: 35


******************************************************************
From:  smith%stku01.uucp@nac.no

Subject: DR-DOS 5.0 with networked Windows 3.0


Help!  I appear to have a problem getting a netwoked version of
Windows 3,0 starting under DR-DOS 5.0.  Under various other versions
of DOS (MS-DOS 3.3, 4.01 and earlier 2.xx versions) there is no problem
getting Windows 3.0 to run.

How the networked version works is this; the user is directed to the
directory on the server (the 'H:\WINDOWS\' directory on our VAX and
then the Windows is started by the command, in a batch file: 
C:\WINDOWS\WIN - normally this works fine.

But - under DR-DOS 5.0 I get the initial Windows 3.0 title screen and then
when that clears the hourglass pops up in the middle (I can move it
around the screen, but that's all I can do) and I get a message saying that
it couldn't find the executable Windows file.

Why?

Also it seems that I'm having a little problem with the memory management
 - it just doesn't 'feel' quite right.  Has anyone managed to run ANY
form of Windows 3.0 (i.e. networked or disk based) and can they send me
a copy of their CONFIG.SYS and, perhaps, the relevant bits of their
AUTOEXEC.BAT files?

Please help/advise as I'm goin' up the wall.

Regards, 
 
           Malc Smith.