Upon startup of Opus 9, my networked drives always show the "red Cross" over their respective drive letter.
I would like for all networked drives to log-on automatically at start-up of Opus, so that I do not have to individually "Click them on" if I want access to them.
I searched and looked everywhere but am not able to find a solution to my problem and am very interested in receiving help to resolve this.
Thank you for any suggestions you can offer.
./. 
This is more a Windows question than something specific to Opus. Opus just shows the drives as the OS reports them.
If you want the drives to auto-connect after boot or login the easiest way is probably to put something in your Start menu -> Startup folder which accesses each of the drives.
If you google for "auto connect network drives" there are a bunch of suggestions.
Hi Leo,
Thank you for your quick reply and suggestion on how to fix my "auto- connect networked drive problem".
I consulted many web pages yet I am not able to create a file for my Start menu (as you indicated) - I'm not an IT person (and I do not user any user ID nor password to boot my local machines).
Again, many thanks for your suggestions and I hope that one of these days I'll find out and learn just how to do this.
Open up a DOS command prompt and for every network drive type the following command:
net use driveletter: \<share> /persistent /user:
eg
net use p: \nas\media /persistent /user:joe mypassword
You will only have to do this once and every time you subsequently log in, windows will reconnect your network drives
Hello Ian Hamilton,
Thank you very much for your quick reply and suggestion. I did exactly as you indicated and received this error message:
If I understand this correctly, the command did not work because the mapped network drive is already/assigned/in use by Opus even though it's drive letter has to be clicked to come to live and accessible.
I thought that this would be easy as this problem only happens on my Vista machine and not on any of my XP-Pro boxes.
.
You might wanna try the /DELETE param first to remove any connections and then connect them again within your batch. Or the /PERSISTANT option to reuse a specfic network-drive (that's how I understood the helptext of "net use").
Another option might be to avoid using network-drives ?! I personally do not use them at all, i have a set of "Go \computer1\c$" buttons to access remote machines' drives. This even works without entering password everytime, when you create the same user on all machines and give them the same password.
Out of interest, what doesn't work when the drives are in the disconnected state (with the red X over their icons)?
Oh, all works fine and as it should. I just have to click on the net-worked drive icons with the red cross over them to make them respond and then all is OK.
It's not a big deal to click on a drive icon. I was just puzzled why this only happens on my Vista box and not my other XP-Pro boxes.
Since I had compared all Opus 9 setting on both OS's and they where all the same, I started puzzling and started this post.
I hope I did not post an irrelevant question and if I did, I apologize.
.
Do you mean the drives don't work if you try to access them another way before clicking their buttons? (e.g. You can't jump to a Favorite folder on them directly or similar?)
Don't worry about the question; it's fine. I'm just trying to understand exactly what doesn't work in case it's something that could be improved. It might turn out to be just the way Windows works but maybe Opus can help, too.
Hello Leo,
When the drive icons are covered by the red cross, we have to double-click them to bring them to live either in the drive-icons section or in Favorites.
If they are not clicked-on, they are there but will not react and/or open.
We investigated this matter further and mention it here only in the hope that it might help us - and you. We automatically load Opus at Windows Start-Up
on every machine on the net so Opus 9 is one of the very first programs to load onto our boxes.
All networked drives have the "Reconnect at Logon" checked but do not seem to reconnect as hoped for in every instance.
For example, we have the database of our accounting program on one networked machine and this database is then accessed by
other users on other networked computers. Now, when the drive where the data base is located is temporarily disconnected for whatever
reason from the local net and then reconnected again, the drive will show up in Opus but now with the red cross and the accounting program (in this example)
cannot be opened by the client computers until the respective drive with the red cross is double-clicked and then all works again as it should.
Would you know of some script that would periodically check if networked drives are connected or not, and if not, do the "double-click" trick automatically?.
I hope I do not bother you with our stuff, but since you might have a remedy for our plight, it's worth mentioning it here ........
Again, many thanks for your offer of help and patience for reading it.
This is what I would do.
Create a .bat file somewhere on your computer (example: c:\Reconnect Network Drives.bat). Edit that .bat file by opening it in notepad and enter in something like:
[code]@echo off
echo Disconnecting F Drive
net use f: /d
cls
echo Disconnecting O Drive
net use o: /d
cls
echo Connecting F Drive
net use f: \server\share
cls
echo Connecting O Drive
net use o: \10.0.0.251\share
cls
EXIT[/code]
The "echo" line just displays that in the msdos window that opens.
The "cls" just clears the last print that was on screen once it's finished.
net use driveLetter: /d disconnects the previously mounted drive letter that you want disconnected.
net use drive: \server\share is the new share and drive letter it uses.
as you can see, you can use as many lines as you need. You don't even have to use the echo to print something on the screen either.
Now you can create shortcuts to this .bat file on your desktop for your users to double-click on just in-case the drives go away. And also place a shortcut in your startup folder so all drives get mounted at login.
/persistant works as well but my users are all over a vpn so using that command wasn't a good idea since the vpn wasn't always on.
Hope that helps. I'm sure others might have other ideas.
Hello ktbcrash,
Thank you very much for your detailed reply.
In view of the complexity of this issue, I will just continue clicking on the "red-crossed" drive letters - an action that has always produced the desired results - even though it's not very elegant.
Again, many thanks for your effort and help.