Post #71,578
12/30/02 6:40:26 PM
|
windows problem
From toysys I have a problem that I have been wrestling with since I upgraded to a "fast" machine which might also be related to NTFS. Just something to keep in mind when you are surfing as you might see something related. And, it seems that I am not the only one experiencing this problem, I posted this on a BB and got several responses stating a very similar problem but no solutions. When I switched from a relatively slow system (766 meg CPU, 2-5Krpm 40 Gig drives, 512 Meg SDRAM [66 meg buss]) to my current (2 gig CPU, 2-7.8Krpm 80/120 Gig drives, 512 Meg RDRAM [400 meg buss]) I have been having serious problems (the software and configuration is EXACTLY the same). Some programs can't report the amount of disk space correctly, some will not install, some run fine sometimes and then sometimes "can't read memory at location XXXX" and crash. For the most part these are just inconveniences but there are some programs that always crash at some point before completing. These are programs that use the HD as scratch space (e.g. encoding DVDs to AVI). This leads me to the core issue. The file system is VERY unstable. I have not been able to find the problem. There are no tuning tools in 2K that allows me to enable or disable features to do diagnostics. Here are some of the symptoms (but not all). Explorer incorrectly reports files that are not there and sometimes doesn't show files that are there. The OS claims that files are locked when they are not. In IE I can delete the history list, look at the list and it is empty, close IE, restart IE and the list is still there (figure that one out!). I believe but can't prove that the "can't read memory" is referring to the HD cache. Sometimes there is continuous disk activity (3-4 minutes or more) but no processes running (the memory and CPU resources don't change). I have a CD emulator (file related) that when it loads changes, removes, and reallocates the compressed/emulated drives in no discernable order. All my problems seem to revolve around the HD system. I have run benchmarks agents the system and the results are "all OK", but obviously not. I am thinking I will need to seriously under clock my CPU but I don't like deliberately crippling the system. any ideas? thanx, bill
will work for cash and other incentives [link|http://home.tampabay.rr.com/boxley/resume/Resume.html|skill set]
You think that you can trust the government to look after your rights? ask an Indian
|
Post #71,583
12/30/02 7:18:39 PM
|
Well here is my stab.
That we are dealing with another Memory problem.
First off, does he have Terminators in the open Memory slots?
Second if not, does he have 4 128MB pieces of memory from the same Manufacturer and Class of memory.
Third, change the ordering of the Memory. You be amazed how it'll help finger the bad one... or even solve the problem.
Fourth, if it turns out the Memory is not the problem, look at the Winders drivers for the "High Speed" IDE interfaces. Years ago we started running into problems with Windows 3.1 when the drives started to get to big and fast for it. Sometimes it'd just sit there thrashing. You had to endup enabling some setting... gosh can't rememeber what it was.
Fifth, Are we at SP3 or better on this machine?
Sixth... we might still be seeing the Klez on this machine.
[link|mailto:curley95@attbi.com|greg] - Grand-Master Artist in IT [link|http://www.iwethey.org/ed_curry/|REMEMBER ED CURRY!] [link|http://pascal.rockford.com:8888/SSK@kQMsmc74S0Tw3KHQiRQmDem0gAIPAgM/edcurry/1//|ED'S GHOST SPEAKS!] | Your friendly Geheime Staatspolizei reminds: [link|http://www.wired.com/news/wireless/0,1382,56742,00.html| Wi-Fi Terrorism] comes with an all inclusive free trip to the local Hoosegow! | I'll never tell, my *overly-red* lips are sealed! *wink* *wink* |
|
Post #71,730
12/31/02 11:05:54 AM
|
his response to both you and doc
Bill, Just an update for the posting (this is a reported work around but is still not a permanent fix). The others I have been corresponding with just responded to my last posting and reported that when they added a FAT32 disk (my suggestion along with under clocking) and used that, their problem disappeared! It IS NTFS causing the headache!!!! Still don't know how to fix my problem as I have nearly 200 Gig disk space all NTFS (you can't switch back) and it's 2/3rds full (ouch). Once again I have been shafted by the Mother F#%*$&% at Microsoft!!!
FIRST RESPONSE That we are dealing with another Memory problem.
First off, does he have Terminators in the open Memory slots? Yes there are "terminators" though they are called bridges with "RDRAM".
Second if not, does he have 4 128MB pieces of memory from the same Manufacturer and Class of memory. There are two 256 Meg sticks and they are, of course, the same manufacture.
Third, change the ordering of the Memory. You be amazed how it'll help finger the bad one... or even solve the problem. Tried that, been there done that.
Fourth, if it turns out the Memory is not the problem, look at the Winders drivers for the "High Speed" IDE interfaces. Years ago we started running into problems with Windows 3.1 when the drives started to get to big and fast for it. Sometimes it'd just sit there thrashing. You had to end up enabling some setting... gosh can't remember what it was.
The IDE is an "on board chip set" and I have the drivers loaded that came from the MB manufacturer.
Fifth, Are we at SP3 or better on this machine?
Yes SP3 is loaded
Sixth... we might still be seeing the Klez on this machine. "Klez"??????
SECOND RESPONSE You need the INF files that describe the motherboard particulars to Windows - otherwise it loads "generic" interfaces that know nothing of the particular advantages of this or that chipset.
These were loaded from the manufacturers CD.
This is commonplace on laptops.
For example:
Install Windows 2000 Unpack INF files Restart Windows 2000 What it finds, it finds. What it doesn't, you install manually. No comment here...
Windows is really quite beautiful in its handling of hardware - no doubt because the manufacturers shower Redmond with information. I will have to totally disagree with this statement. Windows sucks when it comes to handling hardware!
thanx, bill
will work for cash and other incentives [link|http://home.tampabay.rr.com/boxley/resume/Resume.html|skill set]
You think that you can trust the government to look after your rights? ask an Indian
|
Post #71,742
12/31/02 12:12:21 PM
|
Okay then...
What is the NTFS Filesystem Fragmentation like?
I have seen thrashing with as little as 5% fragmentation. I run Norton Speeddisk Scheduled EVERY NIGHT.
The Windows Defragmentor works like CRAP. Pickup Norton SystemsWorks at a Local Computer Show from a Software "Vendor", Install it and Defrag it everynight. Tell it to defrag anyway no matter HOW "good" it says it is. I am running a 200G Drive right now... about 70% full... It took almost 3 days for it to optimize it the first time. Now it takes about 20 minutes... at 3AM ;)
As for "Klez" that'd be the Klez Virus.
[link|mailto:curley95@attbi.com|greg] - Grand-Master Artist in IT [link|http://www.iwethey.org/ed_curry/|REMEMBER ED CURRY!] [link|http://pascal.rockford.com:8888/SSK@kQMsmc74S0Tw3KHQiRQmDem0gAIPAgM/edcurry/1//|ED'S GHOST SPEAKS!] | Your friendly Geheime Staatspolizei reminds: [link|http://www.wired.com/news/wireless/0,1382,56742,00.html| Wi-Fi Terrorism] comes with an all inclusive free trip to the local Hoosegow! | I'll never tell, my *overly-red* lips are sealed! *wink* *wink* |
|
Post #71,616
12/30/02 9:56:13 PM
|
Re: windows problem
Yes -
You need the INF files that describe the motherboard particulars to Windows - otherwise it loads "generic" interfaces that know nothing of the particular advantages of this or that chipset.
This is commonplace on latptops.
For example:
Install Windows 2000 Unpack INF files Restart Windows 2000 What it finds, it finds. What it doesn't, you install manually.
Windows is really quite beautiful in its handling of hardware - no doubt because the manufacturers shower Redmond with information.
-drl
|