If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#11
|
|||
|
|||
Problems with additional RAM aand NIC
SNIP
good to hear : Just tried the last of the RAM (256) to bring it up to 1Meg and again the Device Manager reported problems with the Rhine adapter under NDIS and of course no access to the internet via the onboard LAN interface. It said it was either faulty or bad/incorrect drivers. It Control Panel/Network the Rhine adapter properties didn't change. This time I didn't try reloading any drivers but just powered down and removed the 256 RAM stick and powered up again and all OK with 768. FYI whether 768 or 1Meg the POST says the RAM is OK. Any clues? Alan Correction. It is not of course NDIS but Network. Alan |
#12
|
|||
|
|||
Problems with additional RAM aand NIC
Did you get it fixed?
------------------------------------------------------------------------------------------------------------------------- POKER ACTION AT WWW.AZAPOKER.COM |
#13
|
|||
|
|||
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 |
#15
|
|||
|
|||
Problems with additional RAM aand NIC
"éÇÏÒØ ìÅÊËÏ (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 |
#16
|
|||
|
|||
Problems with additional RAM aand NIC
"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 |
#17
|
|||
|
|||
Problems with additional RAM aand NIC
"éÇÏÒØ ìÅÊËÏ (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 |
#18
|
|||
|
|||
Problems with additional RAM aand NIC
Turn off two first lines in config.sys by putting rem in the beginning.
Do you have SCSI CD-ROM? Why there so many SCSI drivers installed? -- éÇÏÒØ ìÅÊËÏ (Igor Leyko) MS MVP Windows - Shell/User "Alan" wrote in message ... "éÇÏÒØ ìÅÊËÏ (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 |
#19
|
|||
|
|||
Problems with additional RAM aand NIC
Ah, ,, with those types of config.sys and autoexec.bat for Win98(SE), your
running in compatibility mode/real mode. Memory is not able to be addressed properly; devices will not be placed properly in the memory environment; etc. , e.g. Windows can't "do it's thing" in real mode, or a mixed real/virtual environment, it is a virtual mode environment. Memory addressing will be your issues concerning your netcard.. and the additional ram (last 256) which now needs resource ranges of it's own. {For a general idea look at the old DOS info regarding emm386 and himem, and their memory limitations, resource usage, etc.. Then question why your trying to use them.} Remove any unnecessary, and preferably all device drivers from config.sys, except, perhaps, the ones for your specific county/keyboard/video arrangements, and himem.sys if needed for extended memory with LEGACY DOS programs (generally games). Though as your using country/keyboard/video specific settings using emm386.exe would appear advisable. You could try to loadhigh or devicehigh those drivers you think you need.. To TEST this, rem out the "device=c:\rmcd\(driver)" lines. If no problems develop, then remove them permanently by creating a copy without them, and renaming the original to "config.org" or something that you will remember as being the original (just in case). Then devicehigh the config.sys drivers you need, and loadhigh (LH) the autoexec. As for the emm386.exe excludes: yes you can manually exclude the net card addresses as well as video, but it is generally necessary ONLY when using real mode drivers. Windows will exclude the addresses if it is necessary (generally found in the device inf). Also, your files and buffers (and perhaps stacks) statements would be considered too small for most modern DOS program usage, and conflicts with Windows 98 defaults. So the question is WHY you have all these things in your autoexec and config in the first place. Do you use DOS mode for something or legacy devices which require them? BTW: I haven't seen an autoexec and config like you have SINCE DOS days. Installing Win95 would have remmed out most of what you have. And since you asked: info for DOS 6.2(2) is not exactly accurate for 7.0. FYI: Safe mode does not start normal drivers, just base defaults, hence you will not find compatibility/real mode drivers causing conflicts when in safe mode. You could try to "step through" a normal startup, and not loading config.sys and autoexec.bat to see the effect, Igor can tell you how to do that. As for the memory in general, several previous discussions have addressed the 1 gig problem in 98.. 768 is the sweet spot, 1 gig is iffy at best. -- MEB http://peoplescounsel.orgfree.com/ "Most people, sometime in their lives, stumble across truth. Most jump up, brush themselves off, and hurry on about their business as if nothing had happen." Winston Churchill Or to put it another way: Morpheus can offer you the two pills; but only you can choose whether you take the red pill or the blue one. _______________ "Alan" wrote in message ... | | "éÇÏÒØ ìÅÊËÏ (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 | | | | | |
#20
|
|||
|
|||
Problems with additional RAM aand NIC
First things first, my "Windows knowledge" is self taught. Since early
retirement I have tried to understand various elements of the Windows software when problems have arisen before making any fixes. (You really miss tech support when you are at home and something goes wrong!) As a result my knowledge is patchy to say the least, strong in some areas - weak in others. The Autoexec and Config sys are as they have evolved over time with this PC, so if there are errors in the content, please let me know. Regarding the SCSI drivers, I had problems some time ago trying to use the CD-ROM from start up and used MS KB article 190303 to resolve it, which it did. This is where the drivers came from. I haven't had any problems since then and the drivers do load in MS-DOS. I will try the REM on those entries later. Alan "éÇÏÒØ ìÅÊËÏ (Igor Leyko)" wrote in message ... Turn off two first lines in config.sys by putting rem in the beginning. Do you have SCSI CD-ROM? Why there so many SCSI drivers installed? -- éÇÏÒØ ìÅÊËÏ (Igor Leyko) MS MVP Windows - Shell/User "Alan" wrote in message ... "éÇÏÒØ ìÅÊËÏ (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 |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
USB peripherals cause CDRW problems | PSRumbagh | General | 1 | May 6th 06 12:29 AM |
Win98se RAM problems SOLVED! | Cloaked | Setup & Installation | 5 | September 15th 04 10:44 PM |
Corrupt history file causing major problems | djlevinson | Internet | 0 | September 6th 04 03:12 PM |
multiple problems with windows 98 after much money & time | jennifer | Improving Performance | 2 | August 31st 04 08:21 PM |
problems with my programs on microsoft ME | anneliese | Software & Applications | 2 | May 14th 04 12:32 AM |