I guess I'm missing something very basic about Win32::SerialPort. The following one-line demonstrates my travail:

perl -MWin32::SerialPort -e "new Win32::SerialPort 'COM1'"

It results in "Access is denied". Is there some sort of security somewhere in Windows, that would prevent an administrator account from opening a com port? Or is the naming different? Or is it "in use" until you turn off something or another?

I have a cable modem, just reinstalled Win2K Pro, and have not (intentionally) installed any software for use on COM1 (COM2 has my UPS monitoring software).

--
Glenn -- http://nevcal.com/
===========================
Like almost everyone, I receive a lot of spam every day, much of it
offering to help me get out of debt or get rich quick.  It's ridiculous.
-- Bill Gates

And here is why it is ridiculous:
The division that includes Windows posted an operating profit of $2.26 billion on revenue of $2.81 billion.
--from Reuters via http://biz.yahoo.com/rc/031113/tech_microsoft_msn_1.html


So that's profit of over 400% of investment... with a bit more investment in Windows technology, particularly in the area of reliability, the profit percentage might go down, but so might the bugs and security problems? Seems like it would be a reasonable tradeoff. WalMart earnings are 3.4% of investment.

_______________________________________________
Perl-Win32-Users mailing list
[EMAIL PROTECTED]
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs

Reply via email to