Search found 927 matches
- Wed Sep 19, 2018 7:45 am
- Forum: Hardware
- Topic: QLSD driver testers sought
- Replies: 50
- Views: 24573
Re: QLSD driver testers sought
Hi Tetroid I too was stumped by this behaviour a while ago, until it was explained in another thread :-) For this reason, I often include a WIN_USE 'win' in the BOOT file that is run from any medium other than WIN (FLP or else a virtual ROM 'BOOT' device that I use some on of my QL units.) In fact, ...
- Tue Sep 18, 2018 2:11 pm
- Forum: Feedback Section
- Topic: Marcel's new QL-SD interface...
- Replies: 0
- Views: 7736
Marcel's new QL-SD interface...
Just wanted to say how impressed I am with Marcel's revised/re-released QL-SD interfaces! Just received them today (double-card and a micro-SD variant), carefully and conservatively packaged - only a couple of days after shipment and the build quality looks excellent. I'll post again after actually ...
- Tue Sep 18, 2018 1:40 pm
- Forum: Hardware
- Topic: Overview of QL SD / CF Solutions
- Replies: 9
- Views: 5181
Re: Overview of QL SD / CF Solutions
Hi Paul Nice set-up! You asked "what is the use of the (undocumented) "JTAG" connector in the middle of the board" As I understand it, the CPLD (or FPGA) that Tetroid has designed at the heart of his expansion card can be re-programmed 'in-place' via the JTAG connection and a sui...
- Mon Sep 03, 2018 10:44 pm
- Forum: Hardware
- Topic: QL-SD problem - help needed
- Replies: 8
- Views: 4476
Re: QL-SD problem - help needed
Hi Andrew Further to the guidance given earlier, you might want to read the installation section of the Minerva Mk1 (or Mk2) ROM replacement as it specifies exactly how to convert an Issue-5 configured for EPROMs to work with the Minerva daughter board - the QL-SD simply takes the original Minerva a...
- Sat Aug 04, 2018 11:01 pm
- Forum: Hardware
- Topic: 8301 (ZX8301, the QL's Master Chip MC) - facts and figures
- Replies: 69
- Views: 29905
Re: 8301
Hanging-on every word, I'm looking forward to the final installment!
- Fri Jul 20, 2018 12:24 am
- Forum: Hardware
- Topic: QLSD driver testers sought
- Replies: 50
- Views: 24573
Re: QLSD driver testers sought
Terrific Marcel!
I'll test this myself over the weekend.
Can't fault your rapid maintenance release-cycle!
m.
I'll test this myself over the weekend.
Can't fault your rapid maintenance release-cycle!
m.
- Tue Jul 17, 2018 1:50 pm
- Forum: Hardware
- Topic: QLSD driver testers sought
- Replies: 50
- Views: 24573
Re: QLSD driver testers sought
Thanks Marcel! If that is the case WIN_CHECK seems to work fine and you need to backup your image files, re-format the SD and copy them over again as they seem to be fragmented. I was careful to copy single WIN files across to the SD card one at a time following a fresh format, but will try this ste...
- Mon Jul 16, 2018 2:35 pm
- Forum: Software & Programming
- Topic: Request for advice: programming a TASK (not a JOB) in C68...
- Replies: 10
- Views: 4899
Re: Request for advice: programming a TASK (not a JOB) in C68...
Hi Norman
I must leave that request with Tobias as the author, but agree that, if he's willing to, it'd make a very interesting article to augment your already highly interesting periodicial
M.
I must leave that request with Tobias as the author, but agree that, if he's willing to, it'd make a very interesting article to augment your already highly interesting periodicial
M.
- Mon Jul 16, 2018 12:05 pm
- Forum: Software & Programming
- Topic: Request for advice: programming a TASK (not a JOB) in C68...
- Replies: 10
- Views: 4899
Re: Request for advice: programming a TASK (not a JOB) in C68...
Just to close the loop on this topic... Tobias has kindly shared with me an example assembler macro that can form the basis of a 'bridge' between assembler and support C routines. Like all the best solutions to a problem, it is simple and elegant (once you factor-in the couple of documented caveats)...
- Sun Jul 15, 2018 11:26 pm
- Forum: Hardware
- Topic: QLSD driver testers sought
- Replies: 50
- Views: 24573
Re: QLSD driver testers sought
Hi Marcel! Thanks for that. OK, so now with your confirmation of the correct (new/extended?) syntax for the WIN_DRIVE command, I see where I was going wrong: I was using WIN_CHECK <drive_num> as a means to determine whether the last WIN_DRIVE <drive_num>,... mount-attempt was successful. Instead, us...