[qwerty12]

I find downloading too slow with 98 ATM . Im connected to the internet by my Netgear Router and Tiscali 256kbps (**** then, they still havnt upgraded me to 1mbps ) and the speed is fine on my other computer with XP. Download speed used to be fine with windows ME and the only big network change in ME was the windows 2000 network stack was included. I have a ME disc and my question is; is it possible to extract the 2k network stack of my windows ME cd and use it on my 98.

BTW Im not bothered about bugs or anything like that.

Thanks in advance to any replies

[jaclaz]

If it is possible, it has to be on MDGX pages:
http://www.mdgx.com/

or you can try the 98SE2ME:
http://www.mdgx.com/98-5.htm#KRM9S
http://www.msfn.org/...showtopic=46349

jaclaz

This post has been edited by jaclaz: 14 January 2006 - 01:29 PM

[qwerty12]

jaclaz, on Jan 14 2006, 08:24 PM, said:

If it is possible, it has to be on MDGX pages:
http://www.mdgx.com/

or you can try the 98SE2ME:
http://www.mdgx.com/98-5.htm#KRM9S
http://www.msfn.org/...showtopic=46349

jaclaz

Thanks for that. The thing is; i already have the 98SEME done but I will look on mdgx's site

[wizardofwindows]

good ole mdgx hes like the jesus of windows 9x .praise the dos god.

[Tihiy]

As far as I know 98SE2ME does not install Windows ME networking stack.

[MDGx]

98SE2ME installs these files from WinME:

DHCPCSVC.DLL
MSTCP.DLL
NDSWAN16.DLL
NDSWAN32.DLL
VGATEWAY.VXD
WSHTCP.VXD
PPPMAC.VXD
WSOCK.VXD
WSOCK2.VXD
REMOTESP.TSP
TSP3216L.TSP
NDISWMI.SYS
WSASRV.EXE
RNAAPP.EXE
LOCPROXY.EXE
LOCPRXY2.EXE
MSWSOCK.DLL
MSWSOSP.DLL
WINNET16.DLL
WL32DLL.DLL
WLDAP32.DLL
WOW32.DLL
WS2_32.DLL
WS2HELP.DLL
WS2THK.DLL
WSCTHUNK.DLL

and others [I can't recall off of the top of my head], which participate one way or another to TCP/IP networking stack and related functions, like TCP, DHCP, WAN, LAN, PPP, WinSock.
Complete list of files replaced by 98SE2ME:
http://www.mdgx.com/98-5.htm#FME

Hope this helps.

[Tihiy]

MDGx, on Jan 16 2006, 02:08 PM, said:

98SE2ME installs these files from WinME:
...
and others [I can't recall off of the top of my head], which participate one way or another to TCP/IP networking stack and related functions, like TCP, DHCP, WAN, LAN, PPP, WinSock.
Complete list of files replaced by 98SE2ME:
http://www.mdgx.com/98-5.htm#FME

Hope this helps.

It is good, however, i'm sure that main improvement in tcpip.sys and it is not included in 98SE2ME. I also don't know which files or registry entries are responsible for it.

[MDGx]

I have tried briefly %windir%\SYSTEM32\DRIVERS\TCPIP.SYS, but didn't notice any improvement, and not sure if I did it right.
The only registry entries I found are under the NetTrans key [example]:

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\NetTrans\0000]
"DriverDesc"="TCP/IP"
"InfSection"="MSTCP.ndi"
"DeviceVxDs"="tcpip.sys,vtdi.386,vip.386,vtcp.386,vdhcp.386,vnbt.386"
"InstallVnbt"="0"
"InfPath"="NETTRANS.INF"
"ProviderName"="Microsoft"
"DevLoader"="*ndis"
"NodeType"="1"
"NTEContextList"="0x00000003"
"DriverDate"="06/08/2000"
"SignedBy"="Microsoft Consumer Windows Publisher"

I probably need to use also NETTRANS.INF from WinME, or at least add tcpip.sys entries to Win98 SE NETTRANS.INF.
I'll do this again 1 day, when I find more time.

[Madars]

well, win9x serves good even with many megabit connection, so problem may not be in TCP/IP stack but in Internet settings. maybe try some other clients (for example use Opera instead of Internet Exploiter), then try to optimize TCP/IP stack settings.

[MDGx]

Madars, on Jan 18 2006, 04:08 PM, said:

well, win9x serves good even with many megabit connection, so problem may not be in TCP/IP stack but in Internet settings. maybe try some other clients (for example use Opera instead of Internet Exploiter), then try to optimize TCP/IP stack settings.

Thanks for the tip.
I'm aware of Win9x/ME internet tweaks, I actually have quite a few posted at my site:
http://www.mdgx.com/modem.htm
Please see also bugs + browsers:
http://www.mdgx.com/brow.htm

The issue Tihiy and I were discussing was about trying to implement [at least some of] WinME TCPIP.SYS functionality into 98SE2ME, respectively into Win98 SE OS.
And I mean that without hexing tcpip.sys or any other files, just by installing tcpip.sys and related files from WinME setup CD, adding necessary registry entries, and [eventually] using relevant NETTRANS.INF settings from WinME.
But so far [haven't tried too hard though] I haven't been successful.

Hope this helps.

[somewan]

MDGx, on Jan 17 2006, 10:18 PM, said:

I have tried briefly %windir%\SYSTEM32\DRIVERS\TCPIP.SYS, but didn't notice any improvement, and not sure if I did it right.
The only registry entries I found are under the NetTrans key [example]:

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\NetTrans\0000]
"DriverDesc"="TCP/IP"
"InfSection"="MSTCP.ndi"
"DeviceVxDs"="tcpip.sys,vtdi.386,vip.386,vtcp.386,vdhcp.386,vnbt.386"
"InstallVnbt"="0"
"InfPath"="NETTRANS.INF"
"ProviderName"="Microsoft"
"DevLoader"="*ndis"
"NodeType"="1"
"NTEContextList"="0x00000003"
"DriverDate"="06/08/2000"
"SignedBy"="Microsoft Consumer Windows Publisher"

I probably need to use also NETTRANS.INF from WinME, or at least add tcpip.sys entries to Win98 SE NETTRANS.INF.
I'll do this again 1 day, when I find more time.

That doesn't look like a good idea - it appears you're trying to load both
the old VxD-based TCP stack as well as the 2K .SYS file. Multiple protocol
stacks attempting to implement the same protocol suite (TCP/IP) usually
do not co-exist peacefully.

If that is really the way WinMe is configured, then there's another
possibility to consider - the TCPIP.SYS may be merely a "wrapper"
rather than a provider of any real functionality. For comparison,
in Win98SE I found a driver called HIDVKD.SYS loaded by default,
and which turned out to be little or nothing more than a wrapper
around VKD.VXD - I disabled it without any (known) side-effects,
except the memory saved (not much).

In any case, I think *NTKERN is required in the DevLoader list (comma-
separated) in order to load a SYS driver. It may be necessary to list
the SYS file under an "NTMPDriver" entry (rather than DeviceVxDs).

[MDGx]

I also thought tcpip.sys would be just a wrapper, but after looking at its file size and code, I believe that it is unlikely. [?]

I haven't found *ntkern under "DevLoader" in the WinME registry for any tcpip.sys entries.
This is the WinME registry key I was trying to "emulate" in Win98 SE [please note that all NetTrans keys use DevLoader=*ndis , which loads ndis.vxd]:

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\NetTrans\0001]
"DriverDesc"="TCP/IP"
"InfSection"="MSTCP.ndi"
"DeviceVxDs"="tcpip.sys,vtdi.386,vip.386,vtcp.386,vdhcp.386,vnbt.386"
"InstallVnbt"="0"
"InfPath"="NETTRANS.INF"
"ProviderName"="Microsoft"
"DevLoader"="*ndis"
"Preemptable"=hex:00,00,00,00
"NTEContextList"="0x00000002"
"SignedBy"="Microsoft Consumer Windows Publisher"

I also noticed that the only place tcpip.sys is mentioned in the WinME registry, is under the NetTrans keys.

This post has been edited by MDGx: 25 January 2006 - 07:38 AM

[PROBLEMCHYLD]

TCPIP.SYS 4.90.3000.0
TCPIP.SYS 4.90.3004.0

Are missing the same 20 functions checked by wdmcheck.

TCPIP6.SYS 5.0.2195.1 is only missing 7 functions.

This post has been edited by PROBLEMCHYLD: 26 July 2012 - 06:34 AM

[jds]

MDGx, on 25 January 2006 - 07:36 AM, said:

I also thought tcpip.sys would be just a wrapper, but after looking at its file size and code, I believe that it is unlikely. [?]

FWIW, this thing lists as "TCP/IP driver" in the version information, whereas by contrast, 'ndis.sys', which is about half the size, lists as "NDIS 3.0 wrapper driver".

Joe.