Yeah, it's totally unbelievable.
At the time it seemed like the most cost effective solution.
And if it wasn't for the fact we have two remote sites where speed is a big issue,
we would have ditched TS2K months ago.
Lucas
-----Original Message-----
From: Ben Petersen [mailto:[EMAIL PROTECTED]]
Sent: Friday, 14 December 2001 2:29 AM
To: [EMAIL PROTECTED]
Subject: RE: Terminal Server 2000 and RBase 6.0
You have to wonder... the wealthiest, most powerful software
company in the world managed to come up with a server process
that can only handle one connection??
Ben Petersen
On 13 Dec 2001, at 18:12, Albert Berry wrote:
> Our solution to both speed and stability has been to find an old W98SE box and set it up as strictly an R:Base server. This works well for us. RBDOS vs W2K is an ongoing test and review situation with PSD Solutions and RBTI and Microsoft. We, at PSD, raised the issue with MS, and they kindly
installed a test system and db on their network, and verified that our results are true - W2K servers, with two or more users, suck.
>
>
>
> Edwards Lucas <[EMAIL PROTECTED]> wrote:
>
> >Hi all,
> >
> >About a year ago we took two reasonably fast, very stable RBase for windows
> >6.0 databases running at separate sites on NT4 servers across two remote
> >LANs, and centralised them, locating them on a Windows2000 Terminal Server
> >and serving them up across our WAN.
> >This has resulted in two very slow, very unstable databases, loss of hair,
> >sanity etc...
> >The slowness is a result of lack of bandwith across the WAN (128k ISDN) and
> >until we go broadband this will be the case.
> >The instablility is a different story.
> >This mainly relates to print jobs, although we are still getting users
> >dumped out of the database for no apparent reason.
> >In most cases when the print job fails:
> >
> >OUTPUT Print.rep
> >WRITE 'PRINT Bla WHERE bla = .bladebla'
> >OUTPUT SCREEN
> >
> >RUN Print.rep
> >ERASE Print.rep
> >
> >it either won't print at all and will dump the user out to the TS desktop,
> >or it will print but will still dump the user out.
> >
> >Mostly the size of the print jobs are only a few kb, but to print to an
> >700/800/900 series HP deskjet can take an eternity. The HP lasers 5P/6P/2100
> >etc. seem quicker and more reliable but still suffer from the same problems.
> >At present we have about 70 network printers running off the server (dual P3
> >733 2Gb ram) and are averaging about 10 RBGTIME sessions and 3 MSACCESS
> >sessions. The users are running a mixture of win95/2000 desktops.
> >
> >We've tried several things including:
> >Making sure the names of the printers are the same at both ends.
> >The local printer ports are set to ECP (HP recommends this).
> >The paper size settings are consistent across client and server.
> >The latest drivers are loaded (windows95 drivers loaded on the server where
> >needed).
> >Tidying up the code:
> >Being meticulous about declaring/clearing variables.
> >Breaking down the code into smaller procedures.
> >
> >Have been scouring this list for similar problems but it seems that
> >TerminalServer2000 is not a common platform amongst you guys (probably for
> >good reason).
> >
> >Any help would be very much appreciated.
> >
> >Regards
> >Lucas Edwards
> >Wesley Mission Brisbane
> >
> >
> --
>
>
>
>
> __________________________________________________________________
> Your favorite stores, helpful shopping tools and great gift ideas. Experience the convenience of
buying online with Shop@Netscape! http://shopnow.netscape.com/
>
> Get your own FREE, personal Netscape Mail account today at http://webmail.netscape.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 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
