Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
I want to build a network disk with Dos 7.1 as provided by Wengier and friends :-) Which version of ifshlp, protman, tcptsr, tiny rfc and all that stuff do I use?
When I run the Windows gui on top will networking still be available?Kev
Just install and set up MSCLIENT or WFW 3.11 on top of MS-DOS 7.1 as normal, no problems at all. Only note that WFW IFSHLP.SYS doesn't support "LASTDRIVE=32" in CONFIG.SYS due to a confirmed bug in WFW IFSHLP.SYS which may cause "blank screen". So, the default value of LASTDRIVE is now Z(26) instead of 32 to get rid of this IFSHLP.SYS bug.
More information is available at:
http://newdos.yginfo.net/msdos71.htm
0 
Sure, Win98 GUI works fine on top of MS-DOS 7.1 as well as 95GUI, 3.1GUI and WFW3.11GUI. But note that the corresponding IFSHLP.SYS is needed.
0
OK. Lets back the truck up:-))
I've created a dos 7.1 network bootdisk that can connect using netbeui and tcp/ip.
Cool. Now I wanna load the WFW or 98 gui on top.
I've had a look thru your MWIN3.img but there's so much going on. All these things being loaded eg. killer, dready, xmxdsk etc. I can mostly follow what's going on.
What is absolutely necessary to load the win.com?Kev
btw what is killer?
0
Killer(a DOS program protector), Xmsdsk, Dready and more are some third-party tools for DOS, so they are not necessary to load win.com. To load Win GUI on top, only HIMEM.SYS, IFSHLP.SYS and a few more are needed.
0
AUTOEXEC.BAT usually doesn't matter. Win3.x/9x GUI will work with or without the programs like killer.exe. But the correct HIMEM.SYS and IFSHLP.SYS must be loaded in CONFIG.SYS.
For example, if you want to start Win98 GUI located in D:\WIN98:
D:
CD \WIN98
WINThat's it.
0
Okey.
This is what I get:
Trying to load WFW:-
"ERROR: PageOverCommit value in system.ini is too large
Decrease the value, or if not present adda setting that is less that 4."
Where do I add the setting?Trying to load 98:-
"Registry File was not found. Registry services may be inpoerative for this session.
XMS cache problem.
While initializing device V86MMGR: Insufficient memory to initialize windows.
File allocation table bad, drive C.Help!
Kev
0
For WFW:
It's a known bug of Win3.x, which only happens if your memory if MORE THAN 256MB. Set "PageOverCommit=2"(or 1) in [386enh] of SYSTEM.INI will fix this problem.
For Win98:
Make sure you did the following(assume the Win98 path is D:\WIN98):
D:
CD \WIN98
WIN(Please don't type D:\WIN98\WIN at once unless you set "winbootdir=d:\win98" in MSDOS.SYS!)
And make sure the correct HIMEM.SYS and IFSHLP.SYS are loaded in CONFIG.SYS.
0
OK. I have added a NOTE of that Win3.x bug in the page:
"Note that there is a bug in Windows 3.x and WFW 3.x, which may cause Win3.x/WFW3.x to show the following message: "PageOverCommit value in SYSTEM.INI is too large. Decrease the value, or if not present, add a setting that is less than 4." when using 386 Enhanced Mode. This ONLY happens IF the memory of your system is MORE THAN 256MB, since Win3.x/WFW3.x has a problem using that much of memory(>256MB~1024MB) as the swap file. To get rid of this problem, just set the value of "PageOverCommit" in [386enh] of SYSTEM.INI to 3 or less, e.g. PageOverCommit=2."
0
Wengier,
Sorry to keep bothering u with this :-(
Now WFW tries to load bombs out and says KERNEL: Inadequate DPMI server.Kev
ps 98 still not working
0
Then, you should check CONFIG.SYS & AUTOEXEC.BAT, though they usually don't matter, they sometimes DO matter if you load certain win-incompatible programs. Please don't say you don't know how to modify these two files. Here are some screenshots to show they absolutely work:
http://newdos.yginfo.net/pic/doswfw.jpg
http://newdos.yginfo.net/pic/dosw98.jpgMore question or problem, please mail me.
0
Did you load the network programs or so before starting Windows? That will be the main cause. YOU MUST NOT LOAD THEM BEFORE WINDOWS STARTS, NO MATTER WHAT VERSION OF YOUR DOS IS.
0
I trust ya :-))
Just wanna find out why I've got issues.
The only things I load r:
Himem, emm386,ifshlp and set shell=command.com /e:4096 with usual buffers, stacks and files etc in config.sys.doslfn, network drivers and stuff in autoexec.bat.
Really is bare.
Kev
0
"doslfn, network drivers and stuff in autoexec.bat."
So, this is the reason. In order to start WFW 3.x/Win9x GUI on top, you must NOT load "network drivers and stuff" in AUTOEXEC.BAT. Also, WFW 3.x and Win9x require different IFSHLP.SYS, so you can make a dual-boot in CONFIG.SYS, like:
[MENU]
MENUITEM=DOS,MS-DOS
MENUITEM=WFW,WFW 3.11 GUI
MENUITEM=W98,Win 98 GUI[DOS]
bla bla bla..[WFW]
bla bla bla..[W98]
bla bla bla..
0
Don't load them after the GUI has been loaded! Windows GUI(except for Win3.1 or earlier) is not compatible with these network drives from MSCLIENT 3.0 or so! That's why in Response Number 14 I said you'd better make a multi-boot configuration(among pure DOS, WFW 3.11 GUI and Win98 GUI) in CONFIG.SYS if you are not very familiar with these setup.
0
An example is as follows:
CONFIG.SYS:
[MENU]
MENUITEM=DOS,MS-DOS
MENUITEM=WFW,WFW 3.11 GUI
MENUITEM=W98,Win 98 GUI[DOS]
DEVICE=C:\DOS71\HIMEM.SYS
DEVICE=C:\DOS71\EMM386.exe NOEMS[WFW]
DEVICE=C:\DOS71\HIMEM.SYS
DEVICE=C:\DOS71\EMM386.exe NOEMS
DEVICE=C:\WFW\IFSHLP.SYS[W98]
DEVICE=C:\DOS71\HIMEM.SYS
DEVICE=C:\DOS71\EMM386.exe NOEMS
DEVICE=C:\WIN98\IFSHLP.SYS[COMMON]
FILESHIGH=30
BUFFERSHIGH=20
LASTDRIVE=26
STACKS=9,256AUTOEXEC.BAT:
@ECHO OFF
LH DOSKEY
LH DOSLFN
bla bla bla..GOTO %CONFIG%
:DOS
.. <- You can load your network drives here
GOTO END:WFW
C:\WFW\NET START (if needed)
C:\WFW\WIN
GOTO END:W98
C:
CD \WIN98
WIN
GOTO END:END
ECHO Now I'm in MS-DOS prompt.
0
I have got a multiboot config.sys that loads correct ifs and himem.
So then how do I network enable WFW and 98Gui?
Kev
0
Have you seen my response #19?? I believe you didn't.
P.S. I missed the line "DOS=HIGH,UMB" in that CONFIG.SYS.
0
That's more or less how my config.sys and autoexec.bat files look.
Apart from the net start bit in the WFW autoexec.So the network drivers load by default then??
Now I'm double confused :-(
Sorry.Kev
0
WFW and Win98 GUI have built-in network support, so DON'T load other DOS network programs before Windows starts!!!
0
OK. Now I get it.
Phew!
So how do I add new drivers?
Basically trying to get it work with new Dell D600. Have the drivers. How do I incorporate them into WFW?Kev
0
Looks like you are very unfamiliar with Windows network support. Probably you should learn how to setup network support for Windows. I would suggest http://www.wown.com/, which is good place for you to learn the basic knowledge about it.
0  |
 |
 |
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |
