XP parport.sys

Discussion in 'Windows Vista Drivers' started by jim chen, Jun 16, 2004.

  1. jim chen

    jim chen Guest

    I uninstalled ECP LPT1 from XP device manager, and delete parport.sys from
    C:\Windows\System32\DRIVERS, but it AUTOMATICALLY come back after reboot.

    ??? Any idea ?

    I need to develop a parallel port device driver for XP to replace the PARPORT.sys to control my external device.

    does anybody do the similar work ?
     
    jim chen, Jun 16, 2004
    #1
    1. Advertisements

  2. Windows doesn't allow you to replace the system binaries with your own.
    that's an easy path for viruses to get into the system.

    Why not give your binary its own name and service and then set that service
    as the one that PNP loads on the parallel controller instead of parport?

    -p
     
    Peter Wieland [MSFT], Jun 16, 2004
    #2
    1. Advertisements

  3. furthermore, there there is a protocol which allows any driver to control
    the parallel port. look into the parclass IOCTLs.

    d

    --
    Please do not send e-mail directly to this alias. this alias is for
    newsgroup purposes only.
    This posting is provided "AS IS" with no warranties, and confers no rights.
     
    Doron Holan [MS], Jun 17, 2004
    #3
  4. Hello Doron,

    sometimes, it is a good idea to have the driver compiled yourself for
    debugging purposes if you want to use that protocol.

    Regards,
    Spiro.
     
    Spiro Trikaliotis, Jun 17, 2004
    #4
  5. jim chen

    Walter Oney Guest

    Concerning that subject, I had to deal with a horror show for one client
    who wanted to directly control the signal lines on the parallel port. I
    built a driver that used the defined interface by reserving the port,
    etc. The client was still experiencing interference on one of the pins.
    On investigation, I found that the driver for the so-called "Direct
    Parallel" network device (written by a large software company near
    Seattle who shall remain nameless here) was DIRECTLY ACCESSING the I/O
    ports instead of using the IOCTLs.
     
    Walter Oney, Jun 17, 2004
    #5
  6. On investigation, I found that the driver for the so-called "Direct
    IIRC Direct Parallel network device is licensed by MS from some small company.

    The moral of the story: in modern days, it is nearly impossible to make
    parallel-attached hardware other then printers, or make serial-attached
    hardware with timing requirements or with non-standard wire manipulation. Use
    USB for this.
     
    Maxim S. Shatskih, Jun 17, 2004
    #6
  7. and you can always do that, copy it over under another name, and change the
    image path in the parport service key to point to your new binary instead of
    loading the old one.

    -p
     
    Peter Wieland [MSFT], Jun 17, 2004
    #7
  8. Hello Peter,

    yes, I know. I only wanted to point at that there are circumstances
    under which you do not want to use the pp's interface, but use an own
    compiled version instead. It seemed to me Doron thought about it as a
    no-no, and I only showed a legitimate use of it.

    Regards,
    Spiro.
     
    Spiro Trikaliotis, Jun 17, 2004
    #8
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.