Does anyone have any experience of installing QPC2 on a network server?
I'm in the process of writing a program which would be useful to all of us here
at work. In order to demonstrate it, it might be useful to be able to install
QPC2 demo on the server, so that we can all have a QPC2 icon on
Fri, 11 Feb 2005 13:13:17 +,() [EMAIL PROTECTED]
/wrote:
The one thing that I can tell you is that at least my QPC will not share a
QXL.WIN file with another QPC (or uQLx - Q-emuLator for that matter).
Although QPC will start normally, the second another application tries to
use the
Davide Santachiara wrote:
Sorry if I am a bit late but I went a few days in Barcelona and now
I am back with some three hundred message to read...
Ah, I already wondered what took you so long :-)
The speed increase on my Intel Centrino 1,6 Mhz notebook is
impressive. Here are the figures:
Phoebus Dokos wrote:
The one thing that I can tell you is that at least my QPC will not share a
QXL.WIN file with another QPC (or uQLx - Q-emuLator for that matter).
Although QPC will start normally, the second another application tries to
use the QXL.WIN file, the first QPC will not have
Fri, 11 Feb 2005 14:49:40 +0100,() Marcel Kilgus
[EMAIL PROTECTED] /wrote:
Phoebus Dokos wrote:
The one thing that I can tell you is that at least my QPC will not
share a
QXL.WIN file with another QPC (or uQLx - Q-emuLator for that matter).
Although QPC will start normally, the second
Phoebus Dokos wrote:
Hmmm I did not know that WIN_REMV applied to that situation as well (Is it
in the QPC manual?)
Hey, you expect me to know my manuals? You're the user, you should
have read them and be able to tell whether it's in there or not ;-)
But actually, it is:
When a drive is
Marcel wrote:
Quite normally, I guess. But there will be problems when
a) two users trying to start QPC at the same instant (one will get a
Cannot open SMSQE.BIN or something like that).
b) two users trying to access the .WIN file at the same time.
To prevent those problems I did it the following
On Fri, 11 Feb 2005 at 14:46:07, Marcel Kilgus wrote:
(ref: [EMAIL PROTECTED])
Davide Santachiara wrote:
Sorry if I am a bit late but I went a few days in Barcelona and now
I am back with some three hundred message to read...
Ah, I already wondered what took you so long :-)
The speed
Fri, 11 Feb 2005 14:58:32 +,() Tony Firshman
[EMAIL PROTECTED] /wrote:
On Fri, 11 Feb 2005 at 14:46:07, Marcel Kilgus wrote:
(ref: [EMAIL PROTECTED])
Davide Santachiara wrote:
Sorry if I am a bit late but I went a few days in Barcelona and now
I am back with some three hundred message to
In short that means that you cannot have one shared qxl.win across the
network.
Wrong. They can't access it at the same time (i.e. after
OPEN#3,win1_boot WIN1 is blocked for the other machine until you do
a CLOSE#3), but apart from that they can share it just fine.
Marcel
Ah, in my
[EMAIL PROTECTED] wrote:
As long as nobody opens a channel to write to it,
Doesn't matter whether you open the file for writing or only for
reading. The drive will be blocked.
But I just remember one other solution. If you set the .WIN file
attribute to read only in Windows then the QPCs will
Quite normally, I guess. But there will be problems when
a) two users trying to start QPC at the same instant (one will get a
Cannot open SMSQE.BIN or something like that).
I can understand that part. They will just have to be primed to try again when
that happens.
b) two users trying to
This seems quite straightforward, thank you.
A couple of things which worried me were:
1) how to install it on the server - I guess you just put the floppy disk in
the server and install normally. I didn't know if QPC2's installation routine
could handle installing on a server.
2) whether I'd
Ah, great news. That sounds like it will achieve what I want to do.
If the data in the file needs updating (e.g. new forms to add) I could
temporarily un write protect it, update it, and restore normality.
In normal everyday use, nobody will need to write to it. If I need to update
it, I'll
Fri, 11 Feb 2005 15:35:54 +,() Tony Firshman
[EMAIL PROTECTED] /wrote:
On Fri, 11 Feb 2005 at 10:09:25, Phoebus Dokos wrote:
(ref: [EMAIL PROTECTED])
Fri, 11 Feb 2005 14:58:32 +,() Tony Firshman
[EMAIL PROTECTED] /wrote:
On Fri, 11 Feb 2005 at 14:46:07, Marcel Kilgus
On Fri, 11 Feb 2005 at 10:58:03, Phoebus Dokos wrote:
(ref: [EMAIL PROTECTED])
Amstrad 1640)
Also in order to install a third-party HDD (usually a Seagate ST-251-0)
you had to literally use a can opener (for the shielding inside) and
chop a couple of millimetres from the faceplate.
I had no
In message [EMAIL PROTECTED], Wolfgang Uhlig
[EMAIL PROTECTED] writes
Marcel wrote:
Quite normally, I guess. But there will be problems when
a) two users trying to start QPC at the same instant (one will get a
Cannot open SMSQE.BIN or something like that).
b) two users trying to access the .WIN
In message
[EMAIL PROTECTED],
[EMAIL PROTECTED] writes
Ah, great news. That sounds like it will achieve what I want to do.
If the data in the file needs updating (e.g. new forms to add) I could
temporarily un write protect it, update it, and restore normality.
In normal everyday use, nobody
In message [EMAIL PROTECTED], Marcel Kilgus
[EMAIL PROTECTED] writes
Phoebus Dokos wrote:
The one thing that I can tell you is that at least my QPC will not share a
QXL.WIN file with another QPC (or uQLx - Q-emuLator for that matter).
Although QPC will start normally, the second another
19 matches
Mail list logo
