I didn't think anyone else in the ham world had an Entrega 6-port hub! Sad
to say, I had the same experience when moving from W98 to W2K. I tried the
unsupported driver and it worked for some COM operations and not for others.
Never got the specific error message you got, but experienced quite a bit of
system instability that disappeared when the Entrega was uninstalled.
My advice is to ditch the Entrega and get something else. I am not a big fan
of USB-to-COM converters because they depend on the driver to support a wide
range of COM port applications that may or may not be "standard" in the eyes
of the person who wrote the driver. For example, I've never successfully run
the W5XD+ keyer off a USB-to-COM converter because Writelog uses the RS-232
signals for the communications protocol in a way that works but is not
specifically contemplated in the RS-232 standard.
I ended up buying a Byterunner 8-port PCI card. While such cards are also
dependent on their device drivers, I've found that they tend to be more
compatible than USB-to-COM converters. I suspect this is because the PCI
cards have hardware that implements some of the UART functions, while the
USB-to-COM converters do all that in the device driver.
73, Dick WC1M
> -----Original Message-----
> From: David Shipman [mailto:davidshipman@shaw.ca]
> Sent: Thursday, March 04, 2004 1:41 PM
> To: WriteLog@CONTESTING.COM
> Subject: [WriteLog] Writelog and Entrega Sixport Multiport Hub
>
>
> I have a Entrega Sixport Multifunction USD Hub (2USB and
> 4Serial ports) which worked fine on W98. I then upgraded to
> W2000, at which point the Hub disappeared of off the hardware
> list. As some of you may know, Entrega as bought by Xircom
> which in turn was bought by Intel. I downloaded a driver
> (pgwin2k.202.exe) from Intel which is unsupported but did
> bring the Entrega hub back into the system. However, whenever
> I run RTTY (I have a PK-232MBX on Com 3) I run into a
> problem. Opening the RTTY window is ok and running RTTY is
> fine. But if I try to close the RTTY window or try to change
> from PK-232 to a soundcard interface I receive the following
> - " KMODE_EXCEPTION_NOT_HANDLED", this also points to
> "etiserpd.sys" as to where the exception takes place. It
> appears that the driver software is 'broke' I would rather
> not buy a new hub if don't have to.
> If anybody has a software solution to this I appreciate the feedback.
>
> Thanks - Dave
>
> David Shipman (VE7CFD/VA7AM)
> davidshipman@shaw.ca
> Phone: 604-926-8170
> Fax: 604-926-7320
> http://www.bcdxc.org
>
> All outgoing mail scanned by Norton Anti Virus
>
>
>
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
|