Batch file over the network

[Noisy]

I am trying to get some inhouse legacy software to work. This is going to be a bit wordy so hold tight.

Machine using the software: XP

Machine storing the data: Windows 7 Pro

The software is homebrewed. The user selects a vessel and needs to program a hardware key. Our program uses a batch file to call another program. Our program also passes on the vessel's name and path. Striped to the reliant part, this is what is passed to the command line:

 CP32.EXE -U -E"//Font/Master Quad Account/VesselName/Vesselname.128"

With machines running Win XP and Vista this ran without a problem. With Windows 7 the CP32.exe program return a message telling me it could not find the *.128 file.

Other information:

1) Since the Windows 7 machine does not touch a network that is outside of our shop I am currently sharing everything on the machine.

2) I am running the XP machine as an admin. I also created an Admin account on the windows 7 machine that has the same username/password as the XP machine.

3) From the XP machine I can get to all of the reliant folders and have full control via windows.

4) Set up another XP machine. Same problem.

 

[kbrady]

Quick question about the syntax

I don't have an answer for you. this is a very interesting problem.
I am not sure I understand
the syntax. Where the quote marks are used. Without the quote at the beginning I read "-E" as a switch and then I see "//font..." I interpret that part to be a server named "font" with a directory named "Master Quad" and so forth.and this overall represents a complete path. Is that correct?
.
CP 3 2.exe -U -E"//Font/Master Quad Account/VesselName/Vesselname.128"
Kevin

 

[Noisy]

CP32.EXE -U -E -- Program name with two switches
"//Font/ -- Name of the Windows 7 machine on the network
/Master Quad Account/VesselName/ -- path on the Windows 7 machine that holds the file
Vesselname.128" -- Name of the file I am looking for.

The quotes are (or at least were) needed because the command line gets confused by spaces.

 

[kbrady]

Thanks.I wish I could be more helpful. I guess there's a small chance that CMD.EXE is looking for 8.3 filenames but that doesn't seem likely. I'll be interested to see what comes of this.

 

[Barman58]

Couple of things come to mind assuming that the syntax is the same on win7 as it was on XP

Does the actual username on the win7 system exist as a user on the xp machine?
Does this user have sufficient permissions to the files/folders on the XP machine?

Due to the UAC on win7 the user will only be running the batch as a standard user (unless manually elevated) unless the standard user has specific rights to the files it will return a file not found or similar error.

If you assign full control permissions for the actual win7 user this should workaround the issue, unless the actual xp process requires admin credentials. If this is the case then this may be worked around by the use of runas or a scheduled task with the correct syntax

 

[chev65]

Maybe this tutorial on creating batch files will help. http://www.sevenforums.com/tutorials/78083-batch-files-create-menu-execute-commands.html

 

[Noisy]

Barman- Sorry for the delay. Busy week.

Does the actual username on the Windows 7 system exist as a user on the xp machine? Does this user have sufficient permissions to the files/folders on the XP machine?

Tried both. No luck. The Win 7 user is now an admin on the xp machine.

Due to the UAC on win7 the user will only be running the batch as a standard user (unless manually elevated) unless the standard user has specific rights to the files it will return a file not found or similar error.

Since all the program does is read a file on the Win 7 machine and then use it with a program on the xp machine I would suspect that a standard user would be enough. However, I will try giving my xp user specific rights to the file and see if that works.