SCOUG-HELP Mailing List Archives
Return to [ 09 |
March |
2004 ]
<< Previous Message <<
>> Next Message >>
Content Type: text/plain
=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================
J. R. Fox writes:
> waynec@linkline.com wrote:
>
>> As an update to some prior posts, I finally resolved my scsi drive problems;
>> when I installed a new scsi cable the problem ended.
>
> Hi Wayne,
>
> When this was going on, I think I said something about not overlooking the cable
>
> or connectors as possible suspects . . . .
I think I stated that was my prime suspect also. But, the problem occurred
soon after I had made some moves and additions in the box configuration,
starting first on one hard drive, gradually got worse, then started up on
the other. It was not apparent at first that it even WAS a hardware problem.
This is a home computer. New U160 cables are priced in the US $50 to $80+
range, U160 drives are even more expensive, and I had suggestions that heat
might be causing my problems... so, I was looking for a way to pinpoint the
problem, I was not anxious to go out and spend money blindly in hopes it
would resolve the problem.
>
>> Now I am once again having difficulty with my new ActionTec internal PCI
>> modem. Although it didn't work for awhile after I first installed it, in the
>> midst of the scsi problems, the modem was reassigned to IRQ 3 and it worked.
>> Now, after multiple hardware changes while trying to troubleshoot the scsi
>> issue, the modem is once again assigned to IRQ 5 and it is not working. I
>> get a "Could not initialize the port" error message when I try to use
>> Compuserve's CIM program to fetch email.
>>
>> Modifying the DEVICE=D:\OS2\BOOT\COM.SYS (2,CC00,5) statement in config.sys
>> to vary the port address and IRQ does not help.
>
> I have long used SIO as a replacement for the native COM.SYS. I may well be
> wrong
> about this, but I thought that SIO had the ability to force the IRQ assignment,
> so long as:
> those IRQ's were not already in service, there were no BIOS settings conflicts,
> and there
> was no situation where certain PCI slots could *only* support certain IRQ #s.
> My SIO
> lines from CONFIG.SYS are shown below.
>
> DEVICE=E:\SIO\SIO.SYS (COM1,3F8,IRQ4) (COM2,2F8,IRQ3)
> DEVICE=E:\SIO\VSIO.SYS
> REM DEVICE=E:\OS2\BOOT\COM.SYS
> REM DEVICE=E:\OS2\MDOS\VCOM.SYS
>
> Note that the standard issue COM.SYS and VCOM.SYS lines are REMmed out.
>
I can try this, but I'm not sure what setting I would need to use for COM1;
also, if the COM.SYS doesn't seem to work for IRQ 5 (when it formerly was
working for IRQ 3 when the hardware had that IRQ assigned, which doesn't now
work either), why would SIO.SYS be any different?
>> I do not know if/how I can affect the assignment of an IRQ on a PCI device.
>
> Failing that, the only way I know to force IRQ assignments is to take the
> expansion
> cards and play musical slots, until the necessary load order and desired IRQ
> assignments
> have been reached. There should be some combination that works for what you
> have.
> If there is some other trick, maybe someone here will know it.
>
That's what I am hoping.
Thanks for your reply,
Wayne
=====================================================
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
"rollin@scoug.com".
=====================================================
<< Previous Message <<
>> Next Message >>
Return to [ 09 |
March |
2004 ]
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.
|