<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Feb 26, 2010, at 8:29 PM, Bob Wilson, N6TV wrote:</div><blockquote type="cite"><div class="gmail_quote"><div><div class="gmail_quote"><div>What error message do you get? </div></div></div></div></blockquote><div><br></div>Here's the sequence:</div><div> 1. Go to my download directory and right click on "port95nt.exe".</div><div> 2. Click on "Properties", and select "Compatibility" tab.</div><div> 3. Click on "Run in Compatibility Mode for Windows XP Service Pack 2". (Since I've been doing LPT port keying in CT-Win for years on my older machine, under WinXP SP2.)</div><div> 3a. Also click on "Run as Administrator".</div><div> 4. Click on "Apply" and then "OK"; the box closes.</div><div> 5. Double click on "port95nt.exe".</div><div> 6. A new window opens, saying:</div><div> "The following file is already installed on the system: ".....Temp\pft1~tmp\SETUP.INS". (From my previous failed attempts.) Overwrite? I choose "Yes".</div><div> 7. The above repeats for the following files: setup.exe; setup.pkg; setup.iss; setup.ini; _mst32I.EX_; _ISDEL.EXE; _SETUP.DLL; _SETUP.LIB; _SETUP.1; DISK1.ID; _setup.2; Disk2.id.</div><div> 8. After overwriting the last of those files, that window closes and a new one opens with the title: "Unsupported 16-bit Application". The text in the window says:</div><div> "The program or feature "....\Temp\pft1~tmp\SETUP.EXE" cannot start or run due to incompatibility with 64-bit versions of Windows. Please contact the software vendor to ask if a 64-bit Windows compatible version is available. I click "OK".</div><div> 9. Another window is behind that one. It says: </div><div> "Unable to Execute: "...SETUP.EXE /SMS". I click "OK". </div><div>10. The next window says "Package For the Web Error; Unable to execute the specified command line." I click "OK". No more windows.</div><div><br></div><div>If I should then, in a fit of rash optimism, reboot the PC, I get a window following the boot process that says words to the effect of "DLPORTIO.DLL did not install."</div><div><br></div><div>Bud, W2RU<br><blockquote type="cite"><div class="gmail_quote"><div><div class="gmail_quote"><div><br>Once
you get Port95NT.EXE installed and running </div></div></div></div></blockquote><div><br></div>Hah!</div><div><br></div><div><blockquote type="cite"><div class="gmail_quote"><div><div class="gmail_quote"><div><font class="Apple-style-span" color="#000000"><br></font>I hope you're using a real parallel port, not a USB-to-Parallel port interface; those don't work well enough for CW keying.<br></div></div></div></div></blockquote><div><br></div>Agreed. Yes, I have both a motherboard-mounted LPT1 and a PCI card LPT3 in this machine.</div><div><br><blockquote type="cite"><div class="gmail_quote"><div><div class="gmail_quote"><div><br></div><div>Again, what error message to you get? "DLPortIO not loaded?"<br></div></div></div></div></blockquote><div><br></div>Yes, preceded by the same sequence described above.</div><div><br></div><div>There is one more possible "out". One reason I bought Win7 Professional 64 instead of Win7 Home Premium is because with Pro you can download a Windows XP Mode add-on and a Virtual PC add-on for free from MS. I don't know yet whether either of them will do any good. (The former is a 500 MB download -- it's coming in as I type this.)</div><div><br></div><div>BTW, this is a long-festering issue on this machine. I just bought the copy of Win7 Pro 64 but for months I had been running the Win7 Ultimate 64 RCE, and I had the same problem trying to key the parallel ports with CT-Win. I know the ports are there because the key line is activated for perhaps 30 seconds during boot-up; it's just that we hams aren't allowed to get at it.</div><div><br></div><div>Bud, W2RU</div></body></html>