Error 134

4 machine network
1 XP machine, 3 98s
SB2 application

Lately, I've been getting 134 errors.

Only happens if the machines are inactive, like overnight, and if  
application was open.

So, if you forget to close the application, then the next morning you get  
an error 134.  You simply close SB, and restart and the world is fine.   
Happens on all the machines, not just XP.

I suppose the logical question is what kind of network setup "LAN" or 

"distributed LAN", which I should know, but I set this up so long ago
that  
I can't even remember.  And I always have to look up the difference.

Let's see, every machine starts SB from the same drive labeled "G" for
all  
of the computers, but the 98s use slightly different forms and program.  
The data file is all on the G drive. So basically the command line for all  
of them:

G:\SB4W\SB4W.EXE C:\SB4W\CASE51XX.SBP

So I guess this makes this a LAN, not a distributed LAN, right.  I may  
have had a distributed LAN at some point, because I previously had data  
files spread out on various drives because one machine would tend to use  
one file more actively then the others, until I got the XP machine and  
then I decided to put all the data on a drive on that machine but the made  
the forms local to each machine.

At one time, I might have understood the nature of this DOS SHARE error,  
but I don't anymore.

-- 

John,

On Fri, 30 Jun 2006 10:54:22 -0400, John D. Kromkowski
<kromkowski@aol.com> wrote:

> So I guess this makes this a LAN, not a distributed LAN, right.
>


Test for files with extension .SB!

I'm not sure SB4W uses them actually, can't remember, but that would indicate
Distributed LAN.

There is a way to know by looking at your SBLOCK.DLL file, I think by reading
the size of it, but that would be related to which build you have running, and
you might have several.

Then there's LANUSER.EXE, a utility that will set up the LAN you want. I think
you can run that to determine what's in use. You will need your installation
diskettes to run this, I think, or it will complain that the door is open, and
you will have to kill NTVDM.EXE to get out of that loop.

Hope there's something useful here...

IIRC that's the error you'll get if the network disappears and reappears,  
e.g. if you were to turn the network switch your PC is plugged into off  
and on, you'd see err 134

My guess would be it's something to do with the file handles SB is  
expecting to be open being closed by the server for whatever reason.

Phil

On Fri, 30 Jun 2006 15:54:22 +0100, John D. Kromkowski  
<kromkowski@aol.com> wrote:

> 4 machine network
> 1 XP machine, 3 98s
> SB2 application
>
> Lately, I've been getting 134 errors.
>
> Only happens if the machines are inactive, like overnight, and if  
> application was open.
>
> So, if you forget to close the application, then the next morning you  
> get an error 134.  You simply close SB, and restart and the world is  
> fine.  Happens on all the machines, not just XP.
>
> I suppose the logical question is what kind of network setup
"LAN" or  
> "distributed LAN", which I should know, but I set this up so long
ago  
> that I can't even remember.  And I always have to look up the difference.
>
> Let's see, every machine starts SB from the same drive labeled
"G" for  
> all of the computers, but the 98s use slightly different forms and  
> program. The data file is all on the G drive. So basically the command  
> line for all of them:
>
> G:\SB4W\SB4W.EXE C:\SB4W\CASE51XX.SBP
>
> So I guess this makes this a LAN, not a distributed LAN, right.  I may  
> have had a distributed LAN at some point, because I previously had data  
> files spread out on various drives because one machine would tend to use  
> one file more actively then the others, until I got the XP machine and  
> then I decided to put all the data on a drive on that machine but the  
> made the forms local to each machine.
>
> At one time, I might have understood the nature of this DOS SHARE error,  
> but I don't anymore.
>



--