VR Milling Ver 2 on a Network
Moderators: Martin, Steve, Mr Magoo
- bradders
- CNC Guru
- Posts: 1251
- Joined: Mon 13 Feb , 2006 12:35 pm
- Location: Brighouse, England
- Contact:
VR Milling Ver 2 on a Network
VR Milling Ver 2 on a Network
Last edited by bradders on Tue 18 Nov , 2008 9:47 am, edited 1 time in total.
- bradders
- CNC Guru
- Posts: 1251
- Joined: Mon 13 Feb , 2006 12:35 pm
- Location: Brighouse, England
- Contact:
(Only to be carried out by a competent computer technician)
VRMillingDir is where VR is installed (eg "c:\program files\denford\vrmilling") (read only)
InstallDir is where the user can write to (eg "n:\mywork\vrmilling") (read and write access)
Follow this code script in order to allow VR milling to run from a read-only location, but save its settings to a users network drive:
// Create Directories:
Create Directory (InstallDir+'\CNC Files');
Create Directory (InstallDir+'\Tooling Files');
// Copy files:
CopyFileFromTo (VRMillingDir+'\windmill.ini' ------> InstallDir+'\windmill.ini')
CopyFileFromTo (VRMillingDir+'\windmill.mol' ------> InstallDir+'\windmill.mol')
CopyFileFromTo (VRMillingDir+'\windmill.mtd' ------> InstallDir+'\windmill.mtd')
CopyFileFromTo (VRMillingDir+'\machine list.ini' ------> InstallDir+'\machine list.ini')
CopyFileFromTo (VRMillingDir+'\Tooling files\default.mtf' ------> InstallDir+'\Tooling files\default.mtf')
// Change users windmill.ini entries to point to new location (windmill.ini in new location not old):
ChangeIniEntry('Directories','machine list file' -------> InstallDir+'\machine list.ini');
ChangeIniEntry('Directories','XNC Folder' -------> InstallDir+'\');
ChangeIniEntry('Directories','Last Tooling' -------> InstallDir+'\Tooling files\');
ChangeIniEntry('Directories','GNC Folder' -------> InstallDir+'\');
ChangeIniEntry('Directories','FNC Folder' -------> InstallDir+'\CNC Files\');
ChangeIniEntry('Tooling','Tool File name' -------> InstallDir+'\Tooling files\Default.mtf');
ChangeIniEntry('EditForm','FormatFile' -------> InstallDir+'\windmill.ini');
// check machine list.ini in users file location:
change all entries to full paths are pointing to VRMillingDir
eg,
[Millers]
ROUTER=C:\Program Files\Denford\VRMilling\config\
ROUTERV3=C:\Program Files\Denford\VRMilling\config\
ROUTERV3PRO=C:\Program Files\Denford\VRMilling\config\
ROUTERNS=C:\Program Files\Denford\VRMilling\config\
...............
// Create a new shortcut to master exe, changing the "Start In" folder to InstallDir.:
Shortcut.Target:=VRMillingDir+'\windmill.exe';
Shortcut.Description:='VR Milling User';
Shortcut.WorkingDirectory:=InstallDir+'\';
Now run VR from the new shortcut, and the "cannot write to ...." messages will hopefully go
To get VR Milling to run from the server on a client machine
without reinstalling on each client:-
Where:-
P: is mapped to Server programs files (exe's)
N: is clients own mapped drive
1. From the client (with N: drive mapped) run the file "millingUser.exe"
2. Select "install VRMilling user directory"
3. Point to users drive (eg, P:\Denford\VRmilling)
4. Now, the necessary files will be copied from the server to the users
own drive, and a shortcut created which will run the VRMilling exe from the server (P: drive)
5. To add other users, it may be possible to copy this first setup into
other users drives.
VRMillingDir is where VR is installed (eg "c:\program files\denford\vrmilling") (read only)
InstallDir is where the user can write to (eg "n:\mywork\vrmilling") (read and write access)
Follow this code script in order to allow VR milling to run from a read-only location, but save its settings to a users network drive:
// Create Directories:
Create Directory (InstallDir+'\CNC Files');
Create Directory (InstallDir+'\Tooling Files');
// Copy files:
CopyFileFromTo (VRMillingDir+'\windmill.ini' ------> InstallDir+'\windmill.ini')
CopyFileFromTo (VRMillingDir+'\windmill.mol' ------> InstallDir+'\windmill.mol')
CopyFileFromTo (VRMillingDir+'\windmill.mtd' ------> InstallDir+'\windmill.mtd')
CopyFileFromTo (VRMillingDir+'\machine list.ini' ------> InstallDir+'\machine list.ini')
CopyFileFromTo (VRMillingDir+'\Tooling files\default.mtf' ------> InstallDir+'\Tooling files\default.mtf')
// Change users windmill.ini entries to point to new location (windmill.ini in new location not old):
ChangeIniEntry('Directories','machine list file' -------> InstallDir+'\machine list.ini');
ChangeIniEntry('Directories','XNC Folder' -------> InstallDir+'\');
ChangeIniEntry('Directories','Last Tooling' -------> InstallDir+'\Tooling files\');
ChangeIniEntry('Directories','GNC Folder' -------> InstallDir+'\');
ChangeIniEntry('Directories','FNC Folder' -------> InstallDir+'\CNC Files\');
ChangeIniEntry('Tooling','Tool File name' -------> InstallDir+'\Tooling files\Default.mtf');
ChangeIniEntry('EditForm','FormatFile' -------> InstallDir+'\windmill.ini');
// check machine list.ini in users file location:
change all entries to full paths are pointing to VRMillingDir
eg,
[Millers]
ROUTER=C:\Program Files\Denford\VRMilling\config\
ROUTERV3=C:\Program Files\Denford\VRMilling\config\
ROUTERV3PRO=C:\Program Files\Denford\VRMilling\config\
ROUTERNS=C:\Program Files\Denford\VRMilling\config\
...............
// Create a new shortcut to master exe, changing the "Start In" folder to InstallDir.:
Shortcut.Target:=VRMillingDir+'\windmill.exe';
Shortcut.Description:='VR Milling User';
Shortcut.WorkingDirectory:=InstallDir+'\';
Now run VR from the new shortcut, and the "cannot write to ...." messages will hopefully go
To get VR Milling to run from the server on a client machine
without reinstalling on each client:-
Where:-
P: is mapped to Server programs files (exe's)
N: is clients own mapped drive
1. From the client (with N: drive mapped) run the file "millingUser.exe"
2. Select "install VRMilling user directory"
3. Point to users drive (eg, P:\Denford\VRmilling)
4. Now, the necessary files will be copied from the server to the users
own drive, and a shortcut created which will run the VRMilling exe from the server (P: drive)
5. To add other users, it may be possible to copy this first setup into
other users drives.