Problems with additional RAM aand NIC

"AZApoker" wrote in message
oups.com...
Did you get it fixed?

--------------------------------------------------------------------------
-----------------------------------------------

POKER ACTION AT WWW.AZAPOKER.COM

Well, I was puzzled why the Rhine adapter in the Device Manager doesn't have
any problems at 768 but does at 1024. So I spent time surfing the VIA and
ASUS websites. In short the version of the VIA LAN driver I was running was
3.14 and the latest is 3.15. What this actually means is that FETND5A file
was the old version from VIA. In attempting to upgrade the drivers this
morning resulted in the well know bug in Win98SE of not finding drivers in
the Cab files on the CD, so I aborted the load and just tried again and it
worked ok The drivers have all reinstalled (Microsoft included. The
installer left the newer files as well, so I am satisfied the upgrade went
ok). I shall let the system run for a couple of days to ensure that all is
OK and then will try the additional RAM again. I will update as soon as I
try again.
Alan

"AZApoker" wrote in message
oups.com...
Did you get it fixed?

--------------------------------------------------------------------------
-----------------------------------------------

POKER ACTION AT WWW.AZAPOKER.COM

Well, I was puzzled why the Rhine adapter in the Device Manager doesn't have
any problems at 768 but does at 1024. So I spent time surfing the VIA and
ASUS websites. In short the version of the VIA LAN driver I was running was
3.14 and the latest is 3.15. What this actually means is that FETND5A file
was the old version from VIA. In attempting to upgrade the drivers this
morning resulted in the well know bug in Win98SE of not finding drivers in
the Cab files on the CD, so I aborted the load and just tried again and it
worked ok The drivers have all reinstalled (Microsoft included. The
installer left the newer files as well, so I am satisfied the upgrade went
ok). I shall let the system run for a couple of days to ensure that all is
OK and then will try the additional RAM again. I will update as soon as I
try again.
Alan

Can you post or attach memory resourses list? I suppose System information
has it or change a view in a device manager for memory resources.

--
éÇÏÒØ ìÅÊËÏ (Igor Leyko) MS MVP Windows - Shell/User

"Alan" wrote in message
...

"AZApoker" wrote in message
oups.com...
Did you get it fixed?

--------------------------------------------------------------------------
-----------------------------------------------

POKER ACTION AT WWW.AZAPOKER.COM

Well, I was puzzled why the Rhine adapter in the Device Manager doesn't
have
any problems at 768 but does at 1024. So I spent time surfing the VIA and
ASUS websites. In short the version of the VIA LAN driver I was running
was
3.14 and the latest is 3.15. What this actually means is that FETND5A file
was the old version from VIA. In attempting to upgrade the drivers this
morning resulted in the well know bug in Win98SE of not finding drivers in
the Cab files on the CD, so I aborted the load and just tried again and it
worked ok The drivers have all reinstalled (Microsoft included. The
installer left the newer files as well, so I am satisfied the upgrade went
ok). I shall let the system run for a couple of days to ensure that all is
OK and then will try the additional RAM again. I will update as soon as I
try again.
Alan

Can you post or attach memory resourses list? I suppose System information
has it or change a view in a device manager for memory resources.

--
éÇÏÒØ ìÅÊËÏ (Igor Leyko) MS MVP Windows - Shell/User

"Alan" wrote in message
...

"AZApoker" wrote in message
oups.com...
Did you get it fixed?

--------------------------------------------------------------------------
-----------------------------------------------

POKER ACTION AT WWW.AZAPOKER.COM

Well, I was puzzled why the Rhine adapter in the Device Manager doesn't
have
any problems at 768 but does at 1024. So I spent time surfing the VIA and
ASUS websites. In short the version of the VIA LAN driver I was running
was
3.14 and the latest is 3.15. What this actually means is that FETND5A file
was the old version from VIA. In attempting to upgrade the drivers this
morning resulted in the well know bug in Win98SE of not finding drivers in
the Cab files on the CD, so I aborted the load and just tried again and it
worked ok The drivers have all reinstalled (Microsoft included. The
installer left the newer files as well, so I am satisfied the upgrade went
ok). I shall let the system run for a couple of days to ensure that all is
OK and then will try the additional RAM again. I will update as soon as I
try again.
Alan

"éÇÏÒØ ìÅÊËÏ (Igor Leyko)" wrote in message
...
Can you post or attach memory resourses list? I suppose System information
has it or change a view in a device manager for memory resources.

This is what I have just found in the Device Manager for the Rhine adapter:-
Interrupt Request 03
Memory Range E9000000 - E90000FF
Input/Output Range A800 - A8FF
Memory Range 000D0000 - 000D17FF

This is when it is working OK. I don't have the information for when it
appears to be faulty.
Alan

"éÇÏÒØ ìÅÊËÏ (Igor Leyko)" wrote in message
...
Can you post or attach memory resourses list? I suppose System information
has it or change a view in a device manager for memory resources.

This is what I have just found in the Device Manager for the Rhine adapter:-
Interrupt Request 03
Memory Range E9000000 - E90000FF
Input/Output Range A800 - A8FF
Memory Range 000D0000 - 000D17FF

This is when it is working OK. I don't have the information for when it
appears to be faulty.
Alan

"Alan" wrote in message
...
Can you post or attach memory resourses list? I suppose System
information
has it or change a view in a device manager for memory resources.
This is what I have just found in the Device Manager for the Rhine
adapter:-
Interrupt Request 03
Memory Range E9000000 - E90000FF
Input/Output Range A800 - A8FF
Memory Range 000D0000 - 000D17FF
This is when it is working OK. I don't have the information for when it
appears to be faulty.

do you have emm386 or any other memory manager in config.sys? Try to remove
it if yes.

--
éÇÏÒØ ìÅÊËÏ (Igor Leyko) MS MVP Windows - Shell/User

"Alan" wrote in message
...
Can you post or attach memory resourses list? I suppose System
information
has it or change a view in a device manager for memory resources.
This is what I have just found in the Device Manager for the Rhine
adapter:-
Interrupt Request 03
Memory Range E9000000 - E90000FF
Input/Output Range A800 - A8FF
Memory Range 000D0000 - 000D17FF
This is when it is working OK. I don't have the information for when it
appears to be faulty.

do you have emm386 or any other memory manager in config.sys? Try to remove
it if yes.

--
éÇÏÒØ ìÅÊËÏ (Igor Leyko) MS MVP Windows - Shell/User

"éÇÏÒØ ìÅÊËÏ (Igor Leyko)" wrote in message
...
"Alan" wrote in message
...
Can you post or attach memory resourses list? I suppose System
information
has it or change a view in a device manager for memory resources.
This is what I have just found in the Device Manager for the Rhine
adapter:-
Interrupt Request 03
Memory Range E9000000 - E90000FF
Input/Output Range A800 - A8FF
Memory Range 000D0000 - 000D17FF
This is when it is working OK. I don't have the information for when it
appears to be faulty.

do you have emm386 or any other memory manager in config.sys? Try to
remove
it if yes.

--
éÇÏÒØ ìÅÊËÏ (Igor Leyko) MS MVP Windows - Shell/User


A couple of points. I have copied the Autoexec.bat and Config.sys files
below. I have been browsing the MS Knowledge base and now have some
questions. The path= command, should I have something more specific along
the lines of pointing to the system directory i.e windows/system? (Yes, I am
running the Resource Kit). Also buried deep down in a MS Dos 6.2 User Guide
book, it says that when you use EMM386.exe and you have a Network Adapter
installed that uses RAM, you should exclude the memory addresses that the
network adapter uses, so that Windows won't use the same area of memory. Is
this relevant for Windows 98SE (DOS7) or not and is this what you are
implying by asking me to remove the EMM386 memory manger in the config.sys.
Finally, with the extra RAM installed and starting in Safe Mode, the problem
doesn't exist, so yes it must definitely be a Windows problem somewhere.
Alan

SET CTSYN=C:\WINDOWS
@PATH C:\PROGRA~1\WIN98RK;%PATH%
mode con codepage prepare=((850) c:\windows\COMMAND\ega.cpi)
mode con codepage select=850
keyb uk,,c:\windows\COMMAND\keyboard.sys
Set tvdumpflags=8

DEVICE=C:\WINDOWS\HIMEM.SYS
DEVICE=C:\WINDOWS\EMM386.EXE
device=c:\windows\COMMAND\display.sys con=(ega,,1)
Country=044,850,c:\windows\COMMAND\country.sys
device=c:\rmcd\oakcdrom.sys /D:mscd001
device=c:\rmcd\btdosm.sys
device=c:\rmcd\flashpt.sys
device=c:\rmcd\btcdrom.sys /D:mscd001
device=c:\rmcd\aspi2dos.sys
device=c:\rmcd\aspi8dos.sys
device=c:\rmcd\aspi4dos.sys
device=c:\rmcd\aspi8u2.sys
device=c:\rmcd\aspicd.sys /D:mscd001
device=c:\rmcd\flashpt.sys
files=10
buffers=10
dos=high,umb
stacks=9,256
lastdrive=z

"éÇÏÒØ ìÅÊËÏ (Igor Leyko)" wrote in message
...
"Alan" wrote in message
...
Can you post or attach memory resourses list? I suppose System
information
has it or change a view in a device manager for memory resources.
This is what I have just found in the Device Manager for the Rhine
adapter:-
Interrupt Request 03
Memory Range E9000000 - E90000FF
Input/Output Range A800 - A8FF
Memory Range 000D0000 - 000D17FF
This is when it is working OK. I don't have the information for when it
appears to be faulty.

do you have emm386 or any other memory manager in config.sys? Try to
remove
it if yes.

--
éÇÏÒØ ìÅÊËÏ (Igor Leyko) MS MVP Windows - Shell/User


A couple of points. I have copied the Autoexec.bat and Config.sys files
below. I have been browsing the MS Knowledge base and now have some
questions. The path= command, should I have something more specific along
the lines of pointing to the system directory i.e windows/system? (Yes, I am
running the Resource Kit). Also buried deep down in a MS Dos 6.2 User Guide
book, it says that when you use EMM386.exe and you have a Network Adapter
installed that uses RAM, you should exclude the memory addresses that the
network adapter uses, so that Windows won't use the same area of memory. Is
this relevant for Windows 98SE (DOS7) or not and is this what you are
implying by asking me to remove the EMM386 memory manger in the config.sys.
Finally, with the extra RAM installed and starting in Safe Mode, the problem
doesn't exist, so yes it must definitely be a Windows problem somewhere.
Alan

SET CTSYN=C:\WINDOWS
@PATH C:\PROGRA~1\WIN98RK;%PATH%
mode con codepage prepare=((850) c:\windows\COMMAND\ega.cpi)
mode con codepage select=850
keyb uk,,c:\windows\COMMAND\keyboard.sys
Set tvdumpflags=8

DEVICE=C:\WINDOWS\HIMEM.SYS
DEVICE=C:\WINDOWS\EMM386.EXE
device=c:\windows\COMMAND\display.sys con=(ega,,1)
Country=044,850,c:\windows\COMMAND\country.sys
device=c:\rmcd\oakcdrom.sys /D:mscd001
device=c:\rmcd\btdosm.sys
device=c:\rmcd\flashpt.sys
device=c:\rmcd\btcdrom.sys /D:mscd001
device=c:\rmcd\aspi2dos.sys
device=c:\rmcd\aspi8dos.sys
device=c:\rmcd\aspi4dos.sys
device=c:\rmcd\aspi8u2.sys
device=c:\rmcd\aspicd.sys /D:mscd001
device=c:\rmcd\flashpt.sys
files=10
buffers=10
dos=high,umb
stacks=9,256
lastdrive=z