|Posted on Sunday, August 20, 2000 - 11:39 am: |
The latest bug is a missing, "WINMSD.EXE" whose entry point can not be found. And a message that says that
"The Procedure entry Point SetFmleTime could not be located in the dynamic link library Kernel 32.Dill"
This computer was a custom made computer, to be use for creating 3-D graphic and video work.
It is using a Supermicro Dual P6-DKF mother board with a pair of pentium 300 cpu's, and 7 harddrives hooked up to a pair Promise raid cards, and a GVX1 graphic card is also on the board, along with a video card, for video work.
The operating software is NT4 NTSF.
When it was first put together in the shop for me, it was first booted up with Win95, then NT4. As I said before, there are 7 hard drives. They are all Maxtor DMA drives. The first one is 6.4 Gig, and the other six are 8.4 gig drives. The 6 were set up as a zero raid stripe set, And a Matrox 8 meg PCI graphic card was installed in.
I then loaded in my 3-D graphic software, and soon afterwards, discoveried that it had a memory problem. It would get slower and slower, until it would hang, or crush with a blue screen. The guys who put it togather for me, could not find the problem. Finilly about 2 years later, some one told me that it was the "Matrox" graphic card that was causing the problem, and to replace it. So I did that, and personally installed the GVX1 PCI card and the drivers. The memory problem seem to go away. But a new problem came up, after I had opened a file, and use it for a few mins, it would suddently freeze, hung, then the screen would go black. Once that happen, I would have to shut it down and start over. Finilly one morning, it shut down completely, and I could not open anything in the control panel.
So I took it in to a new guy, who told me that the only way to get back in, was do a clean wipe, and re-install NT. So this was done. But he first had to use a Win98 boot up to get in, and then install all the drives first before he could re-install NT4. After that was done, the 6.4 Gig drive was divide, and all the drivers were installed on drive C, and NT4 on drive D, each was a 2 Gig space, And the 6 drives were divide up in to 2 sets of Raid 3's drives. Then he re-installed the 3-D graphic software.
About a week later, I went in to get it, and took it home. And then I discoveried that I could not open any files in the 3-D graphic software. So I un-installed it, and re-installed it, and it worked fine for while.
Then I dicoveried that the old bug was still there, but much worst. After I had open a file, and use it, and saved the change made to it, I could not open another file, then it would hung, and go black.
Finilly I discoveried that if I left it runing in idle, with out opening anything, after logging on, about 3 to 5 mins later, this message about the "SetFlmeTime" would show up, and then lock up.
So I up graded the service pack from 5 to 6a. Thinking that would help. I also put in a new updated driver for the GVX1 .
But the problem was still there. So I uninstalled the GVX1 drivers, and use the VGA mode, and it runs fine in that Mode, but it is so graining, that its to read any thing.
I am at my wits ends. Does anyone have a idea of whats going on here ?
|Danny Albers (Danny)
|Posted on Sunday, August 20, 2000 - 2:49 pm: |
If it was my computer, I would install win 98 as a duel boot, and try that for a while. See for sure if its an NT issue with compatibility, or if it may be bad memory.
If you have the same problems in Win 98, I would be its hardware, then at least you have a starting point.
If Win98 works good, then you know that it is prolly an NT compatiblity problem of some kind. NT is very very sensitive to incompatible drivers. As I have learned many times.
Also, if you have installed service packs, especially full releases, then you are supposed to reinstall all drivers after that. It is Microsoft's recommended procedure.
|Posted on Tuesday, August 22, 2000 - 11:37 pm: |
Thank-you Danny... I did some calling around about the drivers stuff, because I had never heard this piece of information, that some drivers had to be reinstalled after the service pack was upgraded.
The guy who I usually go to, affrimed this, and explained, that the services pack usually upgrades all drivers, but sometimes it will miss something. So he suggusted that I reinstall the drivers for the Raid cards, and I have two of those in my computer, So I went in to the control panel, to the SCSI Adapters, and found that the drivers for the raid cards were missing, So I reinstalled them, And then took it for a test run, in LightWave, and it crashed, with a blue screen.
So I went back to the control panel, and opened the SERVICES box, and notices that both the "Server" and "Workstation" were set for "Automatic" Startup. Since I am not running a Server, I set it for a "Manual" Startup.
Everything works fine now.
Thank-you for your help, in this matter Dan !
Sincerely from Eugene