Conflics with 2 printers one Local vs Network Printer

[klabaza]

Hi people.

Looks some strange situation, exist one user in the company i work, he use one program that runs in ms-dos, to start that program he run this scrip:

**************************************
@echo off
net use LTP1: /DELETE
net use LPT1: \\ing-printer\HPLaserJ
PATH=S:\Y2KFOX;F:\FPD26;
LY2K /A50 #FOX ML -T
f:\fpd26\ML
**************************************

Is not the only user who runs this programs, 2 more are working without any problems, the ing-printer is one print server running windows 2K if you can see it has the printer connected over the LPT port.

He has one printer connected over LTP port to his computer is one Deskjet 722C, this is the default printer.

The problems stars went he finish working with this old-msdos program, on another windows programs he point his local printer(722c) but that didnt print anything, all the work went to the network printer, and of course appear the icon on his systray saying that the 722c was printing and remove the job saying he finish, but them appear the icon of the network printer saying his is printing and yes he print the documents, but all was trush, of course LasserJet is different to a deskjet drivers.

Them i went to the network printer and he was sending trush.

Them i check the settings, and windows xp has 2 drivers for this printer 720c and 722c i use both divers but the same problem.

Before he was working with another computer without any problems, but that computer was remove because it wasnt doint the job well, but no problems with the printers.

I check the BIOS settings for the LPT port on both computers and found this:
New PC Old PC
3BC 378
Normal Bi-direccional

Change the settings on the new computer to be the same as the old computer test and the same thing and this time i didnt open the old-msdos program, them i remove the printer and test again both drivers and same problem.

This is user is in the Administrator group, because if they dosent appear on that group they cannot use this old-msdos program(i read maybe here or another forum about this, and to use the commands we use on this script they must be part of the Admin group, hope this will be fix on windows vista), this is why this user can remove and install printers.

One thing to note is that went i went to the print server, went he was printing the trush, appear on his display window:

Remote Download Document
*Well plus the info about the job, size, etc.

Ok, them i logon with my domain admin user and test with both printers, and all my test where a success, i send to print to the local printer and print, them i send to the network printer and print. But i didn open the old-msdos program, i repeat the test with my test user of the domain, this user is a normal user that i use on each computer to updates and test stuff, this user on each computer is in the admin group, all test where a success with both users.

Them the problem is only with this user.

Now the thing i need to try is to remove the profile of this user and logon again to create a new profile.

I check if we have some conflics with IRQ, or stuff like that on windows but didnt see anything.

Someone here has been having problems like this, what more can i do..? remove drivers installed, remove the user from his desk or %-(, i am really confuse i dont know what that scrip do to the user profile.

Well anything aboout i will apreciated, i will test next week with my domain user, run the old-msdos program and print with the local printer and see what happend, i will inform you people.

Greetings.

Windows XP Professional sp2 all updates
New computer AMD64 +3000

 

[klabaza]

Good morning people.

Look after some research, i found a very easy solution to this problem, after finish working with the old program, the LPT1 still was pointing to the network printer, dosent matter if we reset the system the LPT1 was still pointing to the network printer.

After i exec in the cmd this command:

NET USE LPT1: /DELETE

The system return back the control of the LPT1 port to the local printer(722c), of course, if i exec again the old-program the problem return back, but with one easy batch after we finish working with the old-program every thing is back to normal.

Will this is how i repair this strange problem, thanks all for your time, greetings.