On Wed, Jun 27, 2001 at 06:06:17AM +0100, Dave Walker wrote:
My DiscOVER can already read CD's if it can get direct sector access (it
can also handle DOS format hard disks if the same can be done).
Unfortunately it appears that none of the current emulators give this level
of access to the
On Fri, 29 Jun 2001 00:20:40 +0100 Q Branch [EMAIL PROTECTED]
writes:
In article [EMAIL PROTECTED], Thierry
Godefroy [EMAIL PROTECTED] writes
On Jeudi 28 Juin 2001 23:42, Tony Firshman wrote:
On Thu, 28 Jun 2001 at 21:16:18, you wrote:
C'est l'exception qui confirme la règle
At 01:12 PM 6/28/2001 -0400, Nasta wrote:
Let me give you an example. Suppose someone implemented SCSI on the Q40.
Then, you could connect an IDE and a SCSI hard disc to it. Boh would use
the QWA file system, but here is the problem: each device would have it's
own copy of the QWA handling code.
On 30 Jun 2001, at 13:33, Marcel Kilgus wrote:
QPC v2.03 together with SMSQ/E v2.99 is now available from the usual
places.
Ins't this great service?
Wolfgang
-
www.wlenerz.com
At 01:33 ìì 30/6/2001 +0200, you wrote:
QPC v2.03 together with SMSQ/E v2.99 is now available from the usual
places.
Issues addressed:
- Severe 16bit sprite cache bug in SMSQ/E v2b98
- 0x0 sized windows now possible in 16bit mode
- SER_USE and PAR_USE fixed
Marcel
Since obviously the link is
Executables can be tested via the FTYP function (type 1 is executable)
of Toolkit 2.
AFAIK you can't recognise Resident Extensions by file type, as they
are type 0 data files like text files, sbasic programs etc, although
some manage to mask themselves as 'executable type' - some versions of
Having downloaded and installed this version, I have found that it is like
working through treacle (mouse operations are very slow and
overshooting happens) and the character definition is not good.
What have I done wrong please?
Regards,
Peter Fox
Dilwyn Jones wrote:
I was writing a pointer driven 'System Set' utility which offers you
facilities to set PAR_USE, FLP_USE, SER_USE, PAR_USE etc. All the
commands seem to work if just entered from SBASIC as commands, which
is why I was having difficulty testing the program - it would work
On 7/1/01 at 7:15 PM Dilwyn Jones wrote:
Executables can be tested via the FTYP function (type 1 is executable)
of Toolkit 2.
Yes, they could also be identified (and some more interesting info gleaned)
from the first couple of bytes, the executable header. Don't remember the
definition of the
Executables can be tested via the FTYP function (type 1 is executable)
of Toolkit 2.
Yes, they could also be identified (and some more interesting info gleaned)
from the first couple of bytes, the executable header. Don't remember the
definition of the top of my head, but I know hex 4AFB
At 10:59 ìì 1/7/2001 +0100, you wrote:
Executables can be tested via the FTYP function (type 1 is executable)
of Toolkit 2.
Yes, they could also be identified (and some more interesting info gleaned)
from the first couple of bytes, the executable header. Don't remember the
definition
In article [EMAIL PROTECTED], [EMAIL PROTECTED]
writes
SNIP
The exception proves the rule
I'm sorry to say that the immediately above is spurious and requires
comment:
SNIP
An interesting new take on the subject. I got my information from my
English lecturer at college who extensively studied
On Sat, 30 Jun 2001 21:19:53 -0500 Phoebus Dokos [EMAIL PROTECTED]
writes:
At 12:20 ðì 2/7/2001 +0100, you wrote:
In article [EMAIL PROTECTED],
[EMAIL PROTECTED]
writes
SNIP
The exception proves the rule
I'm sorry to say that the immediately above is spurious and
requires
comment:
13 matches
Mail list logo
