The Sinclair QL Forum

Chr$ wrote:

mk79 wrote:I thought one had to be German to care so much about a definition, but I stand corrected

Either German and/or a software developer and/or computer geek.

Wish I hadn't resurrected this thread now

Hi Chr$,

I would worry about off-topic thread corruption, this seems to be a symtom of the Forum.

Did you get your problem with understanding how the Q68 works?

Derek_Stewart wrote:

Chr$ wrote:

mk79 wrote:I thought one had to be German to care so much about a definition, but I stand corrected

Either German and/or a software developer and/or computer geek.

Wish I hadn't resurrected this thread now

Hi Chr$,

I would worry about off-topic thread corruption, this seems to be a symtom of the Forum.

Did you get your problem with understanding how the Q68 works?

Oh yes, everything is fine at the moment. I have a nice setup consisting of an original QL that is black and quite boxy and a Q68, both connected via QLNET and both outputting crisp VGA on a switch so they share the same monitor. Excellent for space saving.

Pr0f wrote:But a more expanded meaning - original QL case and using the original video circuitry. This allows for expansions within the case.

Technically Qimi / Minerva / Hermes / QL-SD are all expansions within the machine, and some AT keyboard interfaces fitted internally too - but the 'computer' was still the long black brick.

EXACTLY. My first QL is inside a desktop case, with GoldCard, QIMI, Hermes, DIY (controller) 130 MByte RLL Harddisk (with Dirk Steinkopf hard disk driver) AND a 100% compatible QL keyboard (built it myself, cutting all connections on the keyboard PCB, and rewired myself. The cable [very thin] was also self made, "Fädeldraht in Schrumpfschlauch"). But because of BBQL limited to 512x256 in 4 colours :-(

Pr0f wrote:It does suggest that perhaps we need some new dfinitions? :-)

I think so.

Finally up and running with my Q68.. thanks Dave, great piece of work!!

I never thought I'd need to dust off my old PS/2 bits again!!

Just a quick q.. I couldn't see in my quick search so sorry if already asked and answered .. is there any specific size/make etc SD card preferred or can I use any?

I'm sure this is the first of many!!

Thanks in advance

Peter

Hi Peter,

SDHC cards up to 32Gb can be used with the Q68.

The suplied SDHC card is a Sandisk 4Gb card, with 2 partitions:

Partition 1:
FAT32 Containing QWA container files, which are defined as WIN or QUB drives as appropriate

There are example WIN files: QLWA.WIN, QL/E, Black Phoenix

SMSQ/E is defined as WIN8, LRUN WIN8_BOOT to configure SMSQ/E

Partition 2: FAT16 Containing documentation from "The Distribution", SD CARD Formatting software.

This partition is accessed from the Q68 from device FAT1_ or will mount in Linux or Windows as FAT1

Cheers Dave

Any particular class or is it fairly tolerant?

Told you it wasn't the 1st!! Lol

Peter

xpdualcore wrote:Cheers Dave

Any particular class or is it fairly tolerant?

Told you it wasn't the 1st!! Lol

Peter

Hi Peter,

The SDHC Card bundled with the Q68, is a Clsss 4, which is 4MB/s is seems to work without any problems.

Using faster SDHC cards may increase the data transfer.

xpdualcore wrote:Any particular class or is it fairly tolerant?

The Q68 does not require any specific class.

xpdualcore wrote:Finally up and running with my Q68.. thanks Dave, great piece of work!!

Dave is also a hardware guy here on the forum, but I'm pretty sure you mean Derek.

That's odd.... I bought a PS/2 optical mouse so that I could do away with the old Microsoft ball mouse I was using. Tried it the other day and it was fine with the Q68. All of a sudden, today it doesn't like the optical mouse and gets stuck here: I haven't done anything, honest! I have an identical 2nd optical mouse and it's the same with that. Back to the ball and it's fine again. I'm wondering if I'm going completely mad and that it never worked.... but I'm sure I started QLE and it was working at the weekend.

(the only thing that is possible is that I had some stuff on the ps/2 keyboard and maybe some buttons were inadvertently held down when I first tried it today)