Re: Oh for a back door ...



T i m <news@xxxxxxxxxxxx> wrote:

On Wed, 7 Jan 2009 23:36:12 +0000, usenet@xxxxxxxxxxxxxx (Woody)
wrote:

T i m <news@xxxxxxxxxxxx> wrote:

Hi All,

Well there may well have been one but I couldn't think of it ...

Intel Mini primarily Bootcamping to XP.

I picked up a s/u USB <> Serial converter and tried it under XP and
unsurprisingly it didn't support it straight off. I went into device
manager and looked for the device and vendor info as in OSX but it
wasn't as clear. I picked out what I thought was the right bits of
info and Google took me to a USB utility / test app that replaced the
Windows USB driver. Long story short I then lost all USB access,
including keyboard and mouse. :-(

That is less than ideal.

Indeed!

Suprised it didn't pick it up though, I have a
USB - serial adaptor that was picked up without drivers in OSX and
Windows. You wouldn't think there was much to it, being a serial port.

Being a USB interfaced serial port (rather than a direct hardware port
as such) maybe, but from my experience things like this (and modems)
can be the most tricky.

I haven't had much experience with that as I have only tried to do it a
few times and it worked first time every time.

I don't know if that is because it is easy or I got lucky!
You don't really look into things much if they work though.


It was only after that I thought I could have used Bootcamp to
re-start a Windows install but used my Diag-Boot CD instead of the XP
one (I might have been able to replace the USB driver manually that
way)?

In theory, you should be able to access your windows partition and
remove the driver manually.

From?

Some NTFS writing capable software.

A bit more Googling using the codes found in Profiler landed me on the
Prolific 2303 drivers for OSX and Windows.

I think I've installed the driver for OSX (it went though all the
typical stages) but I can't see the port in the System Profiler? Same
exercise under XP gives me a COM9?

If you have some coms program try running that. Something like ZTerm
would do:
<http://homepage.mac.com/dalverson/zterm/>

Ah, thanks. But should I see the existence of the port in the
profiler? Does this say that it IS there?

USB-Serial Controller:

Product ID: 0x2303
Vendor ID: 0x067b (Prolific Technology, Inc.)
Version: 3.00
Speed: Up to 12 Mb/sec
Manufacturer: Prolific Technology Inc.
Location ID: 0x5d100000
Current Available (mA): 500
Current Required (mA): 100

That says you have the usb-serial interface, but doesn't say much about
the port. if you look at the zterm page there is a section on checking
ports. Actually there is a GUI tool for it too, but I think it may be in
the developer tools



--
Woody
.



Relevant Pages

  • USB BADPAD Quirk broken again
    ... PCI: PCI BIOS revision 2.10 entry at 0xfb240, ... Uniform Multi-Platform E-IDE driver Revision: ... usb.c: new USB bus registered, ... Port indicators are not supported ...
    (Linux-Kernel)
  • RE: xp pro sharing printer
    ... How to troubleshoot network printing problems in Windows XP ... SMB-connected print server ... Incompatible print driver ... and then redirect the port to the network server. ...
    (microsoft.public.windowsxp.security_admin)
  • Re: USB device detection via query registry information
    ... specific parts of a driver. ... it correctly enforces exclusivity to the port ... for Windows being crash-prone? ... serenum opens the port, detects the device, ...
    (microsoft.public.development.device.drivers)
  • Re: Cantt copy to DVD
    ... Driver ... DSP Group TrueSpeechSoftware CODEC: ... Ricoh 1394 Controller May Not Work with Windows XP ... Windows XP Does Not Detect Your New USB Device ...
    (microsoft.public.windows.mediacenter)
  • Re: USB device detection via query registry information
    ... it correctly enforces exclusivity to the port ... WHQL is realistically not going to be able to catch all bugs before shipment, so maybe the answer is for WHQL signing to require a commitment from the driver developer to participate in the BSOD crash dump program and issue timely bug fixes. ... Yes these things would not come free, but is it important to Microsoft to shed the reputation for Windows being crash-prone? ... serenum opens the port, detects the device, ...
    (microsoft.public.development.device.drivers)