file cannot be accessed by the system

Does this problem occur on all workstations? What application are you using? Do you have a recent backup to restore the file? Are you sure this .scr is original program file and not a potential virus?

SCR Files are written by a screen shot utility called CAPTURE, included in some of the DOS Versions of Microsoft Word. SCRs are derived PCX files. Notice that CAPTURE can also write ASCII dumps in .LST files.

You could use something like Sentinel File Integrity Checker > http://www.runtimeware.com/Sentinel2.zip
Also use Ivanview to see the contents of the file > http://www.downloadseeker.com/download.php?id=2005&mode=primary

The ownership seems correct: my user and all administrators are owner.

It's an old (from before windows) DOS program.
A local IT-company programmed it and updated it to be y2k and euro compatible.

The backup is corrupted so no, i don't have a backup, I can probably get the original file from the retailer.
The .scr is surely part of the program and not a potential virus. If i start the program it goes looking for this file but gets an access denied.

I still have to check out the tools you suggest and will get back on that.

Thanks,

Niko.

With the sentinel app all files passed integrity check.
When I try to open the file with ivanview I get a black screen (no content?).
Note: this .scr file is from before win32 screensavers existed, I think it is a file made in C++ or something like that.
Could the problem be that Win2k3 SBS recognizes this file (because of the .scr extension) as being a screensaver/executable?

Thanks,

Niko.

You said that backup is corrupted, so, there is a possibility that the file is corrupted as well.
You say access denied error. Does it give you dos error code 5? Or something similar?

I still need to know if the access error occurs on all systems.
Have you tried running the program directly of the server?
I also suggest running chkdsk on your server, log in as administrator then try to move the file.

You could use Bart's PEBuilder to boot from a CD and copy the files using it to another place on your network (and probably burn to CD later so you have a stable copy)....and it's free.
Thanku Bart

http://www.nu2.nu/pebuilder/

JB

scr files could be mistaken by the system as screensavers or as scripts, which they both aren't, and this could be causing your error. You could try deleting the .scr key from the registry in HKEY_CLASSES_ROOT. Make sure you make a backup of this key first.

Just an idea, try to turn on simple file sharing to see if it helps at all:

To turn Simple File Sharing on or off in Windows XP Professional, follow these steps:
1.      Double-click My Computer on the desktop.
2.      On the Tools menu, click Folder Options.
3.      Click the View tab, and then select the Use Simple File Sharing (Recommended) check box to turn on Simple File Sharing.

It is only possible to run the program directly on the server. On the workstations it immediatly closes after starting it.
I do not get an error code. The program still works but can't acces the .scr files.
It says: file D:/path\file.scr not opened.
chkdsk gives no errors.

I'm still reading about the PEBuilder, and will get back on that.

Removing the .scr from the registry doesn't help, same result (not opened).

Simple file Sharing: I'm using Windows Small Business Server 2003 Premium not Win XP Pro.
I can't find the option Simple File Sharing in the menu you described.

Greets,

Niko.

Maybe the DOS program isn't really networkable. Also make sure you can see the file in the above drive and path (D:\path\file.scr). Maybe you have setup your drive mappings to another drive. There could be some configuration files which point to the path and drive of the scr file. Possibly you have to change those settings or run a setup or configuration Tool for the program where these parameters can be set.

""It is only possible to run the program directly on the server""

Why don't you create a folder called profiles and add a batch file for every user. I use Windows 2003 server and Win98 pc's ( Remote users with Terminal Service Client installed). On connection, for example user T20 logs in, T20.bat file runs, maps V: drive, maps Laser printer on LPT1 and dot matrix printer on LPT2. We are using two DOS point of sale and accounting systems.

Sample of batch file:
net use v: \\kcserver\data /yes
net use LPT1: \\10.0.21.20\hp /yes
net use LPT2: \\10.0.20.33\brother /yes
V:
CD VISION
C:\WINDOWS\SYSTEM32\CMD.EXE /K VMENU.EXE

This can also be achieved like this:
In Computer Management, double click the user name, go to Environment, and check the box reading Start the following program at logon. Just add the details pointing to the batch file here.

Mapping a network drive is the most common way of sharing files, and running POS or Accounting programs over a network. What i have done for my local users is this. I installed remote desktop which i have downloaded from Microsoft. I can't remember the url, but you can search for the file >msrdpcli.exe<. It works on all windows OS.

If you have XP pc's on your network, you can use remote desktop from startmenu, programs, accessories, communications, remote desktop connection. Using this method of connecting to the server, you will have all your work stations up and running in no time, cause now all users are opening the accounting program directly of the server, and not over the network.

The program can't use network paths, but with drive mapping it does work.
But that's not really the problem, the problem is that the DOS-program can't access the .scr files, no matter if it is run directly on the server or on a workstation.
I asked the software vendor for a 'clean' installation to see if that works.

Greets,

Niko.

.scr in windows means screen saver. Maybe the antivirus Real-time protection blocks the access to these files as possible viruses. Disable Anti-Virus real-time protection and retry.

Good luck,
Zvitam.

No reply? Please return to question. :-)

Sorry,

I forgot about this thread.
We have decided not to put any more time in this problem.
We will stop using this program since the software vendor can't even provide us with decent support or a clean installation.

Thanks for trying to help anyways.

Niko.