Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Database & SysAdmin
  3. System Admin
  4. Windows XP question

Windows XP question

Scheduled Pinned Locked Moved System Admin
questioncsshelp
1 Posts 1 Posters 3 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • F Offline
    F Offline
    fd9750
    wrote on last edited by
    #1

    Hi All, I have a pretty fundamental question about XP. First some background though. We have an application that works under 95, 98, Me and NT4. An essential part of it is that during operation it substitutes the normal windows drivers handling the communication ports (COM1,2,3,4 etc...) with another driver (made by Willies Computer Software Company in Texas. When execution finshes it restores the normal windows driver. Under the versions mentioned above that works without a hitch. Under windows 2000 it does not because win2000 does not allow the normal driver to be replaced/suspended. Documentation on win2000 says it does but it certainly does not. As Xp is a further evolution of win2000 neither does XP allow you to do that. Bottom line is we cannot make our application work because we need the WCSC driver becuase that one does perform another task which all normal windows drivers are supposed to be able to do but do not (another flaw in the driver that does not do what is specified). Question: I have recently been told that when installing "incompatible" (older) software on an XP system you can tell XP it is supposed to treat it as if it were a windows 98 or NT type application. I was told that when running the application it would then work more or less normally. Question is: does anyone know if this applies to the drivers as well ? if so, is it likely to work ? any help much appreciated, Filip

    1 Reply Last reply
    0
    Reply
    • Reply as topic
    Log in to reply
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes


    • Login

    • Don't have an account? Register

    • Login or register to search.
    • First post
      Last post
    0
    • Categories
    • Recent
    • Tags
    • Popular
    • World
    • Users
    • Groups