mrx100

Alec§taar, thanx for paying so much attention to this say highly-extinct problem. Sometimes the old stuff is really useful...to remind us what was it all about in the beginning Take it easy in your discrete point 8)

Alec§taar, well...Please tell me how often do you print using DOS-progs running under XP? I mean an old 16-bit based stuff. I'm just curious too Don't you think it's a rare thing? So who REALLY cares how it goes within NT core since it's completely out of date? IMHO...that's why such a LPT-based problem happens. I repeat - no matter how many sheets of paper you gonna print knocking on that disconnected LPT - it remains asleep...At least I couldn't wake it up. Only STOP/START method works. You try it yourself, please. Respect.

Well. Have some "news" about the thing Adamvjackson actually first part of the script must be corrected like this net use LPT1: /delete say (1) but the second one net use LPT1 \\printserver\port say (2) is OK Then. The trouble is when I used the batch in a single file during startup it didn't work. But when I had divided it in two that was a success. I run first batch (1) during the startup (as a scheduled task). Second batch (2) is started on logon (same way). May be it's enough to run a single batch just on logon but I didn't try cos was rather sutisfied with the result. Why is it so complicated? We should remember that in case of the port mapping on XP it's a usual thing when the mapped port LPT goes to "disconnected" status after a certain time of inactivity (when there's no printjobs). The same thing happens when you start up the system - the default status of LPT just after the system is loaded is "disconnected". And it's impossible to reconnect LPT making a printjob - it remains notresponding. The only way to solve the problem is to run those two commands on startup and logon and say "refresh" the connection of the mapped port starting it just before you gonna print using mapped LPT if it's in a "disconnected" status (you can monitor that using net use).

adamvjackson, thanx a lot! I'll definitely try that. Let's hope it's gonna be OK

Hi all. Same problem but slightly different. Namely, there's a port LPT1: which is mapped to some remote print server via TCP/IP. In order to map the port I use the following: net use LPT1: \\printserver\remoteport The port is mapping easly with no problems no matter which kind of network protocols is used - IP adress ( for instance \\192.168.0.100\remoteport) or NetBIOS like above. Everything works OK...until the system is rebooted. After the reboot when using net use in console I see that the mapped port is not responding (by the way all mapped drives have OK status anyway ) The question is following. How could I unload the mapped port like LPT1: using console commands? I'm just gonna force this kind of "disconneting" of LPT1: during the shutdown of the system and from the other hand always connect the port using net use when the system is booting up. Looks kinda funny but gonna work I hope if there's a way to dismount the mapped port.