![]() |
|
|
|
|
1
16th March 22:52
External User
Posts: 1
|
Gabor,
Hmmm, that sounds like a bug in XP - it "kind of works" but breaks down. Perhaps something that has been or will be addressed in a service pack? I haven't applied the net share / net use trick on XP in real life, I only know that it "is supposed" to be supported. It sounds like a good idea to suspend use of that feature until those problems have been ironed out, at least as far as LPT1 is concenrned. But on the other hand, I generally recommend against redirecting any printer to a port which is physically present in the computer since it can confuse other applications. In 99% of the cases there is one physical LPT port and nothing else, so I redirect to LPT2 and LPT3. With my LanMan Library functions you can use for example LPT3 for all redirections and connect and disconnect any number of printers, one at a time, to the same local port. That shouldn't interfere with the LPT1 port no matter what the remaining bugs in XP are. What are your other reasons for suspending XP use completely? We have probably discussed it before, but my brain is getting old <g>. For "normal" use by Clipper applications, including redirecting network printers using the LanMan Library functions, I have found that XP works equally well as NT and 2K. By the way, are we talking about XP Home or XP Pro? Perhaps your clients are on the Home version. I know that mine are using Pro. Here is a quote from Steve Quinn today regarding XP Home: "XP Home is seriousyl defective on Networking (total waste of time IMO, XP Home that is<g>) You might find info here - http://www.jsiinc.com/ about how to work around it's networking problems". Klas ------- klas dot engwall at engwall dot com Spammers, please use this address :-) mailto ostmaster@[127.0.0.1] |
|
|
|
|
|