Could someone help on this, I no zip about networks.
This is from a network guy that is trying to setup 6.1
runtime on a 2003 network, 1 server, 1 workstation
(desktop), 1 workstation (wireless laptop)
thanks Marc
I suggested putting the Rbase.cfg and ini only on the
server.
The way it's setup now is as follows, across three
computers. 1) Server 2) Workstation 3) Laptop (laptop
is wireless too).
1) Installed the Server first. Pinnsoft (Program Files
and Data Files) is installed to D:\ClientApps\PinnSOFT
and D:\ClientApps\RBwtime.
PinnSOFT starts this way at the Server. Then
closed PinnSOFT at the server. (the rbase.ini files
point to these paths)
2) Installed PinnSOFT to the Workstation (Program
Files Only) and adjusted the icon and rbase.ini to
reference the P: drive.
PinnSOFT starts this way at the Workstation.
3) Installed PinnSOFT to the Laptop (Program Files
Only) and adjusted the icon and rbase.ini to reference
the P: drive.
Both the Workstation and the Laptop have a P:
(network) drive on the Server which is the root of the
PinnSOFT folder.
The rbase.ini files at both the Workstation and the
Laptop are identical. I removed the rbase.ini file
from the P:\ drive so that it wouldn't conflict with
the rbase.ini files at both the Workstation and the
Laptop.
Starting PinnSOFT from the Laptop first makes it say
the database is corrupted and must be restored from a
backup. When you select to restore from a backup,
(entering Z) it says checking the backup for errors.
Then "no errors" is displayed, but then a message says
"the backup is corrupted too" or must have been moved
somewhere else.
But starting PinnSOFT from the Workstation first is
working without errors. Then while its open on the
Workstation, you can open it on the Laptop with the
only message of "someone else is still in the
database" and when you OK past that, you get in.
It seems to require having the Workstation opened
first. THere is no peer-to-peer happening here
either, but in essence, this network looks like a peer
network in that both the Laptop and the Workstation
are connected to the Server. Incidentally too,
without the rbase.ini file sitting on the server
D:\ClientApps\PinnSOFT directory, the server now
cannot start PinnSOFT because it says it cannot fine
the message file. But here that should be okay because
we're not actually going to run PinnSOFT at the
Windows Server console.
Perhaps what we're going to have to do, is uninstall
and reinstall everything as a peer to peer network,
with the FrontDesk PC (our Workstation) being the
drive that is shared, but then that defeats the
purpose of having a Windows 2003 Small Business Server
(where all the files are getting backed up late
evening each day).
I hope that other people who are using this on a Small
Business Server can shed some light here.
__________________________________________
Yahoo! DSL Something to write home about.
Just $16.99/mo. or less.
dsl.yahoo.com
--- RBASE-L
================================================
TO POST A MESSAGE TO ALL MEMBERS:
Send a plain text email to [email protected]
(Don't use any of these words as your Subject:
INTRO, SUBSCRIBE, UNSUBSCRIBE, SEARCH,
REMOVE, SUSPEND, RESUME, DIGEST, RESEND, HELP)
================================================
TO SEE MESSAGE POSTING GUIDELINES:
Send a plain text email to [email protected]
In the message SUBJECT, put just one word: INTRO
================================================
TO UNSUBSCRIBE:
Send a plain text email to [email protected]
In the message SUBJECT, put just one word: UNSUBSCRIBE
================================================
TO SEARCH ARCHIVES:
Send a plain text email to [email protected]
In the message SUBJECT, put just one word: SEARCH-n
(where n is the number of days). In the message body,
place any
text to search for.
================================================
