Path: chuka.playstation.co.uk!scea!greg_labrec@interactive.sony.com
From: ryan@entrophica.com (Ryan Wilhm)
Newsgroups: scea.yaroze.problems.pc
Subject: Yaroze serial port fried?
Date: Sat, 22 Nov 1997 23:21:13 -0600
Organization: Entrophica Productions
Lines: 26
Message-ID: <MPG.ee1793f2e15f049989680@news.scea.sony.com>
NNTP-Posting-Host: slip129-37-238-79.mn.us.ibm.net
X-Newsreader: Anawave Gravity v2.00.779

Hi everyone,

At one point a few weeks ago, my Yaroze setup was working perfectly. I 
had a huge project that was due at work, and didn't have any opportunity 
to use the development system. (I was focusing mostly on design and 
content in my spare time for these weeks...) So I fire it up earlier this 
week, and to my surprise, SIOCONS can't find the Yaroze... I swapped the 
mouse and yaroze com ports, same thing. (I made sure the environment 
variable that SIOCONS uses reflected these changes.) Plus, there are no 
hardware conflicts, IRQ, address or otherwise, being reported by windows. 
I also made sure to crank the idle sensetivity all the way down in the 
window I was running SIOCONS in, just to make sure windows wasn't 
preempting SIOCONS, which I had trouble with initially during 
downloads...

I've read about the Yaroze frying COM ports on the PC side... can the 
reverse happen? Anybody run into these difficulties? I'd test the cable, 
but the Yaroze side seems to be nonstandard, and I really don't want to 
mess with this sort of stuff. I haven't checked, but is there any line of 
support for hardware problems like this? (As in repair, if this is indeed 
a blown port or something...)

Any responses would be appreciated.

Thanks,
Ryan