Re: Network Issue
- From: "Dave P" <dvs_bis@xxxxxxxxxxxxx>
- Date: Wed, 21 Dec 2005 21:32:57 GMT
my opinion....is do not use exospace..
use blinker.......thats my opinion
I just did a test with blinker 7.0
i created a test protected mode exe
started on my windows network (domain)
on a windows 98 machine
and on a windows 2000 machine
then created a new updated exe
copied it over the exe running on the network
and one machine was running the new exe the others
still the old exe
so blinker in this test does not lock the executable
it is completly loaded intoo memory(real or virtual) by windows
make ur executables protected mode
....
Not Real Mode
Real mode is mix between protected and overlaid (internal/external) overlays
dave
"Robert J. Stuart" <rjstuart@xxxxxxxxxxxxx> wrote in message
news:kHiqf.8085$3Z.5014@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Dave, most of my user terminals are just dos boxes with no HD. I use a
> unique floppy with a unique network and computer name to boot them to dos.
> The autoexec on the floppy then logs the computer into the server and
> directs it to a startup directory where I call a batch file that
determines
> what application that machine is to run. I have over 70 terminals on out
> POS system and this was the down and dirty (cheap) way of doing it. I
need
> to come up with another plan. Am I correct that Exospace does the same
> thing, locks the .exe if a terminal is running it? And am I correct in
that
> there is no switch settings in Blinker to turn off the "dynamic" part of
the
> linker?
>
> Bob S.
>
>
>
>
> "Dave P" <dvs_bis@xxxxxxxxxxxxx> wrote in message
> news:Omiqf.44464$Zv5.14878@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> > here is what i do....
> > you have a network.. and log in scripts
> > Run your exe on local machine..... this will also be faster
> > have a update folder on the network....
> > when user logs into the network
> > Check for updates and copy them too the user folder
> >
> > terminal services
> > same as above but copied too user home folder for your application
> >
> > there are also other ways....the 2 above are just a few
> >
> > dave
> >
> >
> >
> > "Robert J. Stuart" <rjstuart@xxxxxxxxxxxxx> wrote in message
> > news:CDhqf.8808$nm.7227@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> > > When I compiled with S87 and used plink87 as my dynamic linker, as
long
> as
> > I
> > > did not create any overlays using Beginarea / Endarea, the .exe I
> created
> > > would execute from a network terminal with the .exe program on the
> server
> > > without locking the .exe file. Only when I created a dynamic overlay
> > using
> > > Beginarea would the .exe file end up being locked until that terminal
> > exited
> > > the program. I understand the need to lock the .exe when overlays are
> in
> > > use. But many times on the smaller apps, I might change them on the
> fly
> > > and copy the new app to the server while users were still in to an
older
> > > version of that app. Then all I had to do was have the user exit the
> app
> > > and restart it again to update them to the new changes I had made.
> > >
> > > All that being said, now that I am using Blinker instead of Plink87,
> it
> > > looks like all apps created are being locked when executed. Almost
like
> > > Blinker is creating a dynamic linked executable even it not specified
in
> > ,my
> > > .lnk script. So am I crazy or did I miss something? OK forget the
> crazy
> > > part, I really don't want an answer to that one. But am I missing
> > > something here?
> > >
> > > Bob S.
> > >
> > >
> >
> >
>
>
.
- Follow-Ups:
- Re: Network Issue
- From: Robert J. Stuart
- Re: Network Issue
- References:
- Network Issue
- From: Robert J. Stuart
- Re: Network Issue
- From: Dave P
- Re: Network Issue
- From: Robert J. Stuart
- Network Issue
- Prev by Date: Re: Network Issue
- Next by Date: Re: Network Issue
- Previous by thread: Re: Network Issue
- Next by thread: Re: Network Issue
- Index(es):
Relevant Pages
|