The Sinclair QL Forum

Most probably, Turbo reverts to integer division when divididng two integer types (sounds logical, doesn't it?), while SBASIC does what it always does when calculating expressions: It uses a floating point result.

Tobias

RWAP wrote: I seem to recall an online version of Jan Jones book but can't remember if this was OK with her!

I'm pretty sure on a no on that, as she still sells it as an e-book on Amazon.

Tobias

Rich,

the

QDOS Technical Guide

(as available from Dilwyn's site)

Is the definitive source of information and the only thing you actually need (and, all the 80ies developers had) to develop for the original QL.

Tobias

On one of my QLS (a JS model) this seems to have been done at the factory (did never come around to check if really all the mods were done), or at a pretty good repair site, solder joints in no way look different than the others. And well, it works. No idea how it would work without the mods, though...

On a Rest-of-world QL, a timer tick is 1/50s. On a US QL, a timer tick is 1/60s. Video standards are different and the screen resolution is slightly different. I am not sure what exactly would be affected, as most timings in the QL are measured in tight CPU loops that should be the same, but would a...

However, I am getting incorrect results from the DATE function within QPC2_Turbo_compiled tasks : I always get the same value returned at every call ! That's weird. Can't second that. Can you verify this with a simple one-liner (100 PRINT DATE) compiled? Be aware DATE called more than once per seco...

With QPAC2 alone, not a lot. Only executable files are executed What you probably refer to is FileInfo2 and its configuration? Here you can determine what is supposed to happen when a non-executable file is executed. If you have FI2 loaded, you can configure that using FI2Config_obj. So, you might b...

You need to work on your technique! This way round you're going to spill it all!

Cheers,
Tobias

Probably the best solution is for us all to be aware of WHY this executable file problem occurs in the first place, but I guess I will never see the day when nobody downloads a file from my site, unzips it in Windows then claims the zip file is broken. The easiest for this would maybe be a disclaim...

Nice.

Note the BOOT included in the starter1_zip zip file (that seems to be intended to go to WIN1_BOOT) will not work on ROM versions before JS. It loads SuperBASIC extensions and tries to use them in the very same Basic program - This will not work on JM and earlier.

Tobias