OK this thread is way over my head, but I'm reading it - I might even learn
something.
Just to take off at a tangent, how about an open source (type) project to
build a new Operating System for ALL the QLs/compatibles/emulators out thare
to use.
Same hardware, same everything - if at all
At 11:30 ðì 29/6/2001 +0200, you wrote:
Phoebus Dokos wrote:
So probably there is an interim version of SMSQ/E I don't have... probably
through QPC v.2.01 (I had v.2 final)
Yes, v2a98 (supplied with v2.01) is minimum.
Is there anyway I can get it?
It's on its way.
Marcel
After a quick
On Samedi 30 Juin 2001 13:22, Phoebus Dokos wrote:
After a quick check... Nope!
With SMSQ/E 2a97 and new QPC Turbo still produces the same error.
I never succeed to make Turbo work on a SMSQ/E system (tested
on QXL and QPC2), so I am wondering how it could ever work
for you...
QDOS/SMS
OK this thread is way over my head, but I'm reading it - I might even
learn
something.
I know what you mean; I need to go and have a lie down between each
post :) but I'm trying to follow the thread.
For me, an operating system should boot with built-in support for just
the basic features
At 01:45 ìì 29/6/2001 +0200, you wrote:
On Samedi 30 Juin 2001 13:22, Phoebus Dokos wrote:
After a quick check... Nope!
With SMSQ/E 2a97 and new QPC Turbo still produces the same error.
I never succeed to make Turbo work on a SMSQ/E system (tested
on QXL and QPC2), so I am wondering how it
At 08:40 ðì 28/6/2001 -0500, you wrote:
At 08:03 ðì 30/6/2001 -0500, you wrote:
At 01:45 ìì 29/6/2001 +0200, you wrote:
On Samedi 30 Juin 2001 13:22, Phoebus Dokos wrote:
After a quick check... Nope!
With SMSQ/E 2a97 and new QPC Turbo still produces the same error.
Also with QPC 2 Final and
On what platform ? PC 286 ?
-Message d'origine-
De : Phoebus Dokos [mailto:[EMAIL PROTECTED]]
Envoyé : jeudi 28 juin 2001 15:54
À : [EMAIL PROTECTED]
Objet : Re: TURBO and SMSQ/E (was: Re: [ql-users] New QPC2 release)
On QPC 2v2 FINAL, SBASIC reports execution in 9 secs.
When I
At 02:57 ìì 29/6/2001 +0200, you wrote:
On what platform ? PC 286 ?
Haha :-) No Athlon 750. Maybe it's the memory allocated for qpc (64Megs).
*AND BTW: It was 1 not 1000 ;-)
Anyways when I updated that little program once more and removed SQRT(f), I
replaced it with COS(f), SIN(f),
I saw similar behavior with Qlib versus SBasic (and so stop compiling my
programs) but never test Turbo (faster than Qlib under QDOS but a bit fussy)
Claude
sorry for the question about the platforn : I can't resist %#)
-Message d'origine-
De : Phoebus Dokos [mailto:[EMAIL PROTECTED]]
On Jeudi 28 Juin 2001 16:03, Phoebus Dokos wrote:
H now that's ODD!
I used the following little program to run a benchmark of Turbo of sorts
10 CLS
20 PRINT #2, date$
30 FOR F=1 to 1000
40 PRINT #1, SQRT(F)
50 END FOR F
60 PRINT #2, date$
70 PAUSE
Ooops make the 1000 1
On
Hi
In QLToday May/June page 56 is mentioned a B.Smith who has an Epson Colour
880 printer.
I would like to contact him, anyone know his address, e-mail, phone,
whatever?
Thanks,
Ian Pizer, 49 ch. Machery, 1292 Chambesy, Geneva, Switzerland.
e-mail [EMAIL PROTECTED] tel.41227581410
AKA [EMAIL
At 03:31 ìì 29/6/2001 +0200, you wrote:
I saw similar behavior with Qlib versus SBasic (and so stop compiling my
programs) but never test Turbo (faster than Qlib under QDOS but a bit fussy)
Claude
sorry for the question about the platforn : I can't resist %#)
Oh no worries, I would have done
On Samedi 30 Juin 2001 15:03, Phoebus Dokos wrote:
I never succeed to make Turbo work on a SMSQ/E system (tested
on QXL and QPC2), so I am wondering how it could ever work
for you...
Ha! The fact that it works for me exactly proves why I have NO CLUE in
assembly and C :-)
Seriously now,
Phoebus Dokos wrote:
With the new QPC the PARSER refuses to load with the message that's above.
Well, unfortunately I have no problems with it at all, neither with
your example nor with Thierry's...
Marcel
If the same routine are used it's normal that Turbo add a small overhead (I
think) : in this case it only adds more call
-Message d'origine-
De : Marcel Kilgus [mailto:[EMAIL PROTECTED]]
Envoyé : vendredi 29 juin 2001 17:32
À : ql-users
Objet : Re: TURBO and SMSQ/E (was: Re: [ql-users]
At 05:19 ìì 29/6/2001 +0200, you wrote:
Phoebus Dokos wrote:
With the new QPC the PARSER refuses to load with the message that's above.
Well, unfortunately I have no problems with it at all, neither with
your example nor with Thierry's...
Marcel
H Question Did you do anything
Par_use ser (no quotes) just worked for me - without an error message - on
the latest QPC2v202 with smsq 2b98.
Try removing the quotes.
I don't know if it will actually work, because I'm at work and have a
network printer :o)
Norman.
In fact, it works even with quotes as well !
Maybe it needs a reboot :o)
Norman.
Norman Dunbar EMail: [EMAIL PROTECTED]
Database/Unix administrator Phone: 0113 289 6265
Lynx Financial Systems Ltd.
I need to use the PAR_USE command with an older program which only
prints from SER1
Ideally I would like to use something like PAR_USE 'SER' to make
output sent to ser1 appear on the parallel printer port.
However, if I try PAR_USE SER or PAR_USE PAR even in QPC2v2.02
(freshly downloaded) I
At 08:38 AM 6/29/2001 +0100, Norman wrote:
Just to take off at a tangent, how about an open source (type) project to
build a new Operating System for ALL the QLs/compatibles/emulators out thare
to use.
An interesting idea, Norman. There are some pluses and some minuses:
+ Good way to
On Vendredi 29 Juin 2001 07:14, ZN wrote:
On 6/28/01 at 11:14 AM Thierry Godefroy wrote:
[lots snipped]
OK, this is supposed to be a discussion, not an argument, so let me make
some things clear right here.
I have nothing against arguments (in the debate acceptation of the term,
not in
At 10:21 ðì 29/6/2001 -0700, you wrote:
At 08:38 AM 6/29/2001 +0100, Norman wrote:
Just to take off at a tangent, how about an open source (type) project to
build a new Operating System for ALL the QLs/compatibles/emulators out thare
to use.
An interesting idea, Norman. There are some pluses
[meta-devices]
NO! Channels are meant to exchange DATA, NOT to send COMMANDS or
PARAMETERS to a piece of hardware ! (of course, you could argue
that commands and parameters are just some form of data,
but you won't, will you ? ;-)
This reminds me of how the Apple ][ disk drives were
23 matches
Mail list logo