Mike

I run the DOS and WIN local and network all on the same development machine
without any real hitches. I do this by having a directory holding the rbase.cfg
file and I use the -o option like Razzak has pointed out to get this to work.
The Shortcuts look like this:
In a Win2k shortcut for the Win65 version the Target is ...
C:\RBTI\RBWin65\RBG65.EXE -oc:\rbw65\rbase.cfg -r jim.dat
C:\RBTI\RBWin65\RBG65.EXE -oc:\rbw65\rbase.cfg jim.dat -r

It doesn't seem to matter where the filespec(jim.dat) seems to be placed in
relation to the -r command but the first line is what is recommended in the
docs. In the Win2k shortcut the Start in option in my shortcut is like so...
C:\RBTI\RBWin65\

As you can see the -o option for my windows version's rbase.cfg file I put
in a directory c:\rbw65\ and for the DOS shortcut I use a oc:\rbd65\ directory.

My shortcut for the network Win version is:
K:\rbti\rbwin65\RBG65.EXE -oc:\rbw65\rbase.cfg -r
My shortcut for the network DOS version is:
K:\rbti\RBDOS65\RBASE65.EXE -oc:\rbd65\rbase.cfg -r

   Now this keeps thing somewhat simple, but it still means you have to create
this shortcut each time OR .... you could do what I did..

   I have a directory on the network called RBUsers and a sub-directory for
each user. In the RBUsers dir I have a subdirectory in it called rbcfg. In the
rbcfg directory I have subdirectories (you guessed it -- RBD65 holding the a
default DOS rbase.cfg and another dir RBW65 holding the default Win RBase.cfg.)

   Then I can copy this default directory to the users machine - change the
NAME tag in the cfg file. I also have a predfined shortcut (defined like the
above) for each version. I will drag these to the users desktop and then modify
them to fit what dat or ??? file they are going to run at startup. 
   When I get a user setup, I then COPY all his/her shortcuts and the RBW65 &
RBD65 directories to their individual named sub-directory so I can just COPY
the shorcuts back to their machines when they lose them or their machine is
revamped or ???

In retrospect, the next phase of development for me is to do away with
directories on the users local machine and set up the shortcuts to look at this
already established RBUsers directory on the network, so the shorcut targets
would look like:

K:\rbti\rbwin65\RBG65.EXE -ok:\rbusers\~username~\rbw65\rbase.cfg -r dothis.dat

Hope this helps, I know it's probably more than what you asked for.

Jim Limburg

--- MJS <[EMAIL PROTECTED]> wrote:
> Hi all,
> 
> If you need to put Rbase for DOS and Rbase for Windows on the same computer,
> what do you do with the RBASE.CFG files?  If you are using both on a stand
> alone
> machine, you can just move to the directory where the needed version is, and
> have the correct copy of Rbase.cfg in that directory.  BUT, if you are on a
> LAN,
> and different users might be at the same machine through out the day, each
> user
> may need a customized version of RBase.cfg with at least a change in the line
> that indicates the user's name.  If the program files are located on the
> server,
> you can't have more than one version of Rbase.cfg in the same directory.
> SO......what is the best way to handle that problem?
> 
> TIA!
> 
> Mike Sinclair
> 
> ================================================
> TO SEE MESSAGE POSTING GUIDELINES:
> Send a plain text email to [EMAIL PROTECTED]
> In the message body, put just two words: INTRO rbase-l
> ================================================
> TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED]
> In the message body, put just two words: UNSUBSCRIBE rbase-l
> ================================================
> TO SEARCH ARCHIVES:
> http://www.mail-archive.com/rbase-l%40sonetmail.com/


__________________________________________________
Do You Yahoo!?
Yahoo! Sports - Coverage of the 2002 Olympic Games
http://sports.yahoo.com
================================================
TO SEE MESSAGE POSTING GUIDELINES:
Send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: INTRO rbase-l
================================================
TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: UNSUBSCRIBE rbase-l
================================================
TO SEARCH ARCHIVES:
http://www.mail-archive.com/rbase-l%40sonetmail.com/

Reply via email to