OpenBCM V1.07b12 (Linux)

Packet Radio Mailbox

DB0FHN

[JN59NK Nuernberg]

 Login: GUEST





  
GM7HUD > PACKET   20.06.07 00:17l 28 Lines 1293 Bytes #999 (0) @ WW
BID : 764665GM7HUD
Read: OE7HNT DL6DBA GUEST
Subj: Re: FT817/ IC706/ 9k6 experiments
Path: DB0FHN<DB0FOR<DB0SIF<DB0IDN<DB0MW<DB0ROF<DB0ACH<DB0ACC<DB0GOS<ON0AR<
      GB7YKS<GB7SYP<GB7ESX
Sent: 070619/1735z 68135@GB7ESX.#31.GBR.EU $:764665GM7HUD [Witham, Esx]NNA V3.1


G0FTD wrote:-
> 
> Now the strange thing is that5 under WinXP the printer port data pins
> all sit at high, AGW Packet Engine is unable to key them.
> 
> But WinME treats the printer port properly, and works as I want it
> for keying the rig. A bit odd so I'll try using the serial port to see
> if it's more reliable with WinXP asap.

Because XP owns the hardware and ME doesn't. This is basic OS stuff but
unfortunately not well stood by people who aren't programmers. To them the
fact that XP wont let their old software directly fondle the hardware is a
pain. There are some fine and dandy reasons why any old piece of software
can't just access the hardware but they're rather off-topic.

You need to update your old software to something that asks the OS if it,
the OS which owns the hardware, will fondle the parallel port rather than
being somewhat rude and fondling the port all on its Jack Jones.

However, in an ideal world the user having problems with parallel ports and
AGW would have Googled for "agw xp parallel port" and found the blurb on
the Soundcardpacket web site that says "Stop being a cheapskate Mr. FTD and
pay for the AGWPE Pro version that does what you want!" as AGW does not
work with a parallel port and XP for the reasons stated above. :-)

73 de Andy GM7HUD


Read previous mail | Read next mail


 17.11.2024 10:33:01lGo back Go up