Re: Paradox 8, NETBEUI and a small LAN

#1

It is an XP problem in a mixed environment.

Here is a repeat of an earlier post that might help you some:
-----------------
Hi All,

I got this info from Brian's Buzz (Brian Livingston's new
site/newsletter) which describes much of the XP slowdown stuff we have
been hearing about. It is not confined to Pdox but since it is file
transfer and network traffic related a Paradox ap is likely to exhibit
this more than others. Note that protocol changes are NOT the answer
here. I think some folks who are having this problem should download the
sniffer mentioned and report back on what they find.

http://BriansBuzz.com/w/030619
---------------

Also, search the google newsgroup searches and the search at
pnews.thedbcommunity.com for more threads on this.

Denn Santoro
President
Resource Development Associates
http://www.RDAWorldWide.Com
Offices in the United States and Germany
Providing solutions to health care, business, governments and non-profits
since 1982

#2

Ike wrote:

Quote:

One of the WIn95 PCs is the file server

you'll have many problems if the XP machine is a workstation, with
anything other than 2000 or XP as a server..

--

Steve Green - Diamond Software Group, Inc - Waldorf Maryland USA
Corel CTech Paradox - http://www.diamondsg.com - Support/Downloads/Links
---------------------------------------------------------------------------------

Do you need a Sanity Check? http://www.diamondsg.com/sanity.htm
Upgrade/Downgrade versions? http://www.diamondsg.com/upgrade.htm
-------------------------------------------------------------------------

#3

Hi Ike,

"Ike" <spamminator (AT) spamminator (DOT) com> wrote

Quote:

.... One of the WIn95 PCs is the file server and has a folder
mapped as drive P: and a subfolder NET to handle the sharing (Paradox
Drivers are configured for P:\NET) with all the other PCs accessing
the database on drive P:.

The BDE does not work with NT Clients (inc W2K, XP) accessing a database on
a Win9x Server (inc Me).
Move the database to one of the NT based machines are hopefully things will
sort themselves out.
Leslie.

#4

Leslie,

I that is a little over broad. I have had no real trouble setting up W95 and
W98 to be accessed from NT and W2k. I haven't tried with XP but from what I've
read in the groups THAT is the only combo (XP to 9x) that causes significant
issues.

Denn Santoro
President
Resource Development Associates
http://www.RDAWorldWide.Com
Offices in the United States and Germany
Providing solutions to health care, business, governments and non-profits since
1982

#5

"Dennis Santoro" <RDAPres (AT) RDAWorldWideSPAMFILTER (DOT) com> wrote

Quote:

Leslie,

I that is a little over broad. I have had no real trouble setting up W95
and
W98 to be accessed from NT and W2k. I haven't tried with XP but from what
I've
read in the groups THAT is the only combo (XP to 9x) that causes
significant
issues.

Hi Dennis,

Sorry to disagree, but this has been discussed at length over the last
couple of years on the BDE newsgroup. The general consensus is that the BDE
fails to work correctly when accessing a Paradox database (not sure about
others) on a Win9X server when NT based clients are involved. This surfaces
in a number of ways, usually in lock errors but also General Protection
Errors and even database corruption if a write operation is underway.

This has been *reported* to happen with Win2K clients (as this was when the
problem started to surface). I agree on a lesser extent the NT clients (my
feeling is that it depends upon which service pack).

The fault itself might be directly related to a particular BDE operation,
but it seems these days that programmers are a different breed who would
rather a quick fix than actually try to identify the root cause. This
appears to be the case with many who frequent the BDE newsgroup of late.

The Win95 network fault affects not just the BDE but all LAN applications.
This was fixed in OSR2 and from memory was something to do with vredir.vxd
(or similar).

Leslie.

#6

Also, for anyone having networking issues... I highly recommend referencing
the following site:
http://www.helmig.com/

--
....
`·.¸¸.·´¯`·.¸¸.·´¯`·-> rodney

#7

Here is a good link describing how to manage the Browse Master and also the
effects it can produce:
http://www.wown.info/j_helmig/browse.htm

--
....
`·.¸¸.·´¯`·.¸¸.·´¯`·-> rodney

#8

Could you provide more specific details, please, including the
address of the newsgroup you are referring to, as I have seen
several networks operating perfectly well while using a Win9X
system as a Paradox file server.

Mike

In article <3f02f084 (AT) jedstarmail (DOT) psfloan.com>, CDB4W (AT) bigpond (DOT) com
says...

Quote:

"Dennis Santoro" <RDAPres (AT) RDAWorldWideSPAMFILTER (DOT) com> wrote in message
news:3F02E5D8.104D6C40 (AT) RDAWorldWideSPAMFILTER (DOT) com...
Leslie,

I that is a little over broad. I have had no real trouble setting up W95
and
W98 to be accessed from NT and W2k. I haven't tried with XP but from what
I've
read in the groups THAT is the only combo (XP to 9x) that causes
significant
issues.

Hi Dennis,

Sorry to disagree, but this has been discussed at length over the last
couple of years on the BDE newsgroup. The general consensus is that the BDE
fails to work correctly when accessing a Paradox database (not sure about
others) on a Win9X server when NT based clients are involved. This surfaces
in a number of ways, usually in lock errors but also General Protection
Errors and even database corruption if a write operation is underway.

This has been *reported* to happen with Win2K clients (as this was when the
problem started to surface). I agree on a lesser extent the NT clients (my
feeling is that it depends upon which service pack).

The fault itself might be directly related to a particular BDE operation,
but it seems these days that programmers are a different breed who would
rather a quick fix than actually try to identify the root cause. This
appears to be the case with many who frequent the BDE newsgroup of late.

The Win95 network fault affects not just the BDE but all LAN applications.
This was fixed in OSR2 and from memory was something to do with vredir.vxd
(or similar).

Leslie.

#9

Actually it is not a good idea to put data on a WS. Unless your data is
not worth the cost of a $400 server you are just asking for trouble trying
to share data from a workstation. If you absolutely must do this you have
lots of issues to worry about such as setting the machine role to server,
disabling oplocks, making sure the user never shuts the machine down
unless they are 150% certain no one is connected to their data, etc.

Denn Santoro
President
Resource Development Associates
http://www.RDAWorldWide.Com
Offices in the United States and Germany
Providing solutions to health care, business, governments and non-profits
since 1982

#10

As do I. Have for years since P7. I prefer to go with NT4, Novell or Linux
servers but not all clients will go there.

Denn Santoro
President
Resource Development Associates
http://www.RDAWorldWide.Com
Offices in the United States and Germany
Providing solutions to health care, business, governments and non-profits since
1982