Programmer, thank you that is terrific. Now anyone who is using Win 9x/Me can get their favorite email checker to work more easily using the above IOLED.EXE file.
I am actually dual booting WinMe with Win2k on my iopener, and am pretty much only using the latter for reasons of stability and responsiveness (I just leave it on all the time hanging from my kitchen cabinets, and with a fresh install with SP2 I didnt even have to load any sound/graphics/VIA device drivers). Therefore I for one would be interested in the NT version of IOLED. Laserfan, that's why your workaround wouldn't work for me either.
Since I started this thread last night I did find a shareware NT IO device driver from Upper Canada Technologies which actually includes an OCX. Therefore, I wrote a simple Windows Scripting Host VB script to check my pop account (using a freeware POP object) and set the LEDs accordingly. Unfortunately, this solution is resource hungry, what with wscript, the OCX, a DLL, and the SYS file.... it sleeps at about 2.9Mb according to task manager.
So I for one would be interested if you can create a more elegant solution under NT/2000/XP, so I can avoid this kludged solution.
In any case my wish for the NT device driver version of IOLED.EXE would be not only the EXE (for the simple mail checkers) but also in ActiveX object format for simple WSH scripts. For example, my script blinks the right LED every minute as it checks the POP/Hotmail mailcount, and turns on the left LED if the mailcount>0 and off if it is equal to zero (i.e., Ive checked my mail from another workstation). It sleeps the rest of the time, but does awaken every minute. For those wondering why I use both LEDs like this, I spray-painted my IOpener case blue to match my kitchen, so neither LED is labelled.