said:
>>I moved the video card from one PCI express slot (the blue one) to
>>another one (the black one), and for a while I had no trap errors.
>Has this hardware ever worked 100% reliably?
The motherboard was in my Photoshop computer for two years. However, I had
a different video card -- a PCI Geforce 6200. It worked with my analog
monitor under WinXP and eComStation. It did not work with my analog
monitor under eComStation.
Before I made the transfer, I tried the Radeon X800 PCI Express X16 card,
and under OS/2 it recognized my digital monitor right out of the box. I
did not do any extensive testing with OS/2.
After the transfer to this computer, I don't remember any immediate
problems. I think it was after messing with the SCSI card that I began
having problems, but I can't be sure.
>>With ECS, I also did a unimaint desktop restore and recovered some of my
>>desktop icons, but not all. At least it worked (for a while).
>Odd. It the data was there when you backed it up, it's got to be there
>after the restore. It almost seems like you are have disk read problem.
>>With Warp 4, during the boot, I got the error message "Unicode -- file
>>not found" and I could not get access to some programs nor to the
>>internet.
>This is another indicator of disk read problem. The loader is
>encountering unrecoverable read errors and refuses to load the driver.
>>Then the trap errors started again on both the ECS and Warp 4 partitions
>>-- but not on the maintenance partition nor on Win XP. Both of those are
>>normal.
>Are you sure you are using a sufficiently new version of Dani's drivers?
>SATA support is still evolving.
>>I wrote down some of the trap info -- it is the same on both warp and
>>ecs:
>>Internal processing error at location
>>##0168:fff1dalf0003:calf
>>6000, 9084
>>0786090f
>>The traps occurred just after loading
>>GENM32W.SYS
>This is your wireless driver, IIRC.
No, this is what supports the built in NIC using the NForce 4 chipset.
>>But when I remmed out that statement in both config statements, the trap
>>occured after the previous statement (I didn't write it down, but I
>>think it was Protocol or something like that).
>This is expected. You are getting cascading failures because you did not
>load the NIC driver.
>>I will wait another day or two before pulling this MB and putting back
>>the old one -- it would be nice if I could figure out the problem.
>I see you have answered my question. I think a new Dani driver might be
>useful.
I will play with this for another day, but I have to have a reliable
computer by Monday. Hopefully, putting the old motherboard back in will
work, if I have to resort to that.
It would be nice to figure out the problem with this one. Thanks again for
the help.
Sandy
=====================================================
To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".
For problems, contact the list owner at
"postmaster@scoug.com".
=====================================================
<< Previous Message <<
>> Next Message >>
Return to [ 14 |
April |
2007 ]
The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA
Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS
RESERVED.
SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group.
OS/2, Workplace Shell, and IBM are registered trademarks of International
Business Machines Corporation.
All other trademarks remain the property of their respective owners.