I also have events to capture exiting LCDC: switching the backlight off; and on when starting LCDC.

This, however, doesn't address the suspend/resume catastrophic crash! :wink: Once the driver/LCDC has crashed in NT, that's it... a reboot is necessary to start the display comms again.

May post ...

Looks like a generic NT problem...

Hope this gets fixed...

Now that's what I call international support! Bravo!

Matt: any news on this one?

Anyone else experiencing LCDC crashing when resuming from stand-by in Win2K?

I'm using a LK202-24-USB.

I have a feeling it's the driver, not LCDC... but can anyone confirm this?

I use stand-by quite a lot and obviously this is a bit inconvenient!

Thanks Rob: don't know why I didn't think of that! :)

I can confirm that this workaround is successful, although it's a bit fiddly!

1) Go to Device Manager and change the COM port for the USB device to COM2 and change the baud rate to 19200
2) Remove the standard COM2 from the device list (if you ...

Thanks Henry.

The Alpha Demo could communicate with the screen OK. However, I'm guessing that this is because all of the configuration is manual, rather than querying the installed 9x driver which doesn't seem to report available ports properly(?).

Is a driver update imminent to address this issue ...

Please help a newbie! :)

Although the device in Win98SE is installed and is listed in Device Manager as both COM3 and the USB device, no software can connect to it as they cannot see the device!

So, LCDC on setup goes to COM1... not found, COM2... not found, and back to COM1...

Display Tuner ...