It is possible to run Sage MAS 200 as if it were operating as Sage MAS 90?
The main difference is that you will give up the processing speed because all data will be processed at the workstation instead of the server as it would be under Sage MAS 200. Sometimes for debugging purposes you might want to run Sage MAS 200 as if it was not optimized for client server (ie. Run it as a plain Sage MAS 90 implementation).
Instructions For Version 4.x:
You can run Sage MAS 200 as if it were a Sage MAS 90 installation in one of two ways.
First, map a network drive (UNC does NOT work for Sage MAS 90). Then use Windows Explorer and navigate to \mas90\home on the server drive. Find and run the pvxwin32.exe. When that starts, type in RUN "STARTUP.M4P"
Second, you can modify the standard Sage MAS 200 shortcut icon with the following parameters:
Target:
x:\mas90\home\pvxwin32.exe ..\launcher\sota.ini ..\soa\startup.m4p
Start In: x:\mas90\home
Tip:
a. If you are moving servers and using this setup merely to test an upgrade without having to load onto a full Client Server install, do not forget to disable PC Charge credit card processing (if enabled) or you may unwittingly send credit card transactions on the test setup
b. With respect to (a) above -- also check the data paths in company maintenance for each company - be sure they are pointing to the NEW location and not the old path.
Both of the above (a+b) primarily relate to situations where you are copying a MAS 200 setup to a new location for the purposes of testing an upgrade, etc.
Instructions for Version 3.7x:
Map a drive letter to just above the \MAS90 folder. A UNC mapping will not work. Do not map INSIDE of \MAS90 - you should be able to see \MAS90 from your drive mapping.
There are then two ways to run Sage MAS 200 as if it was Sage MAS 90:
First, use the Windows Explorer to navigate to your \mas90\home folder. Highlight and run PVXWIN32.EXE (typically by double clicking it).
At the Providex Prompt - type in RUN "Sage MAS90"
Secondly, create a Sage MAS 90 shortcut icon by copyng the one for your Sage MAS 200 and modifying it to equal the following:
Target: "x:\mas90\home\pvxwin32.exe" ..\launcher\sota.ini ..\soa\mas90
Start In: "x:\mas90\home"