Nope, it doesn't require a kernel mode driver if you are just doing standard
rs-232 communication..
If you want, I have a simple C++ wrapper around the serial port access
written for VC++..

-R

-----Original Message-----
From: pic microcontroller discussion list
[mailto:PICLIST@MITVMA.MIT.EDU]On Behalf Of Konstantin Klitenik
Sent: Thursday, April 03, 2003 4:41 PM
To: PICLIST@MITVMA.MIT.EDU
Subject: Re: [PIC]: PIC software


Wouldn't access to serial port require a kernel mode driver as well?  I have
no problem with programming parallel port and I already have the kernel mode
driver.
>
> > I think I'm just going to write my own I2C interface and just get the
> > data directly from EEPROM via Parallel Port.  I'm not positive, but I
> > don't think EEPROM chip cares or knows what is talking to it, the pic
> > or par port.  This will eliminate writing pic routines to talk to the
> > computer.  Does anyone think that's not such a good idea and why?
>
>It will be a lot easier to write PIC code to read from an EEPROM and write
>to the serial port than to get low level access to a parallel port in
>Windows.  The latter requires a kernel mode device driver.
>
>
>*****************************************************************
>Embed Inc, embedded system specialists in Littleton Massachusetts
>(978) 742-9014, http://www.embedinc.com
>
>--
>http://www.piclist.com hint: The list server can filter out subtopics
>(like ads or off topics) for you. See http://www.piclist.com/#topics


_________________________________________________________________
Help STOP SPAM with the new MSN 8 and get 2 months FREE*
http://join.msn.com/?page=features/junkmail

--
http://www.piclist.com hint: The list server can filter out subtopics
(like ads or off topics) for you. See http://www.piclist.com/#topics

--
http://www.piclist.com hint: The list server can filter out subtopics
(like ads or off topics) for you. See http://www.piclist.com/#topics