[Ql-Users] PC 5.25 Disk
I have a copy of QL 2 PC here by Transform - I have managed to rescue the QL files from microdrive, but there is a 5.25 disk (presumably for the PC side - as I do not have a manual). Can anyone still read PC formatted 5.25 disks and convert it onto a 3.5 disk? Does anyone have a manual for this? Thanks -- Rich Mellor RWAP Services Specialist Enuuk Auction Programming Services www.rwapservices.co.uk ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
Re: [Ql-Users] DEBUG
Hi Michael On 17 Feb 2012, at 19:25, Michael Bulford wrote: There is some code in my program that I do not want compiled: this is only used when the SuperBASIC version is running. So, I use DEBUG 1 before the code and DEBUG 0 afterwards. When compiling the parser stops with the report of Task Turbo 5.06 halted, after line 0. Reason: out of range The display panel reads: Pass: 1Line 22300, which is a few lines after the DEBUG 1 statement. Can anyone please tell me what I am doing wrong? The program will compile successfully if the DEBUG command is not used. I have tried using DEBUG_LEVEL but this makes no difference. I use DEBUG 0 and 1 for the same reasons as you and have never had the fault you mention. If you could send me, privately, a copy of your program I'll try to locate the problem. George ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
Re: [Ql-Users] PC 5.25 Disk
On 18 Feb 2012, at 08:17, Rich Mellor wrote: Can anyone still read PC formatted 5.25 disks and convert it onto a 3.5 disk? I have a 5 1/4 disk drive. Also PC Conqueror is able to read these disks in PC format. Xover should then be able to produce QL 3 1/4 disks. George ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
Re: [Ql-Users] PC 5.25 Disk
George Gwilt wrote, on 18/Feb/12 10:14 | Feb18: On 18 Feb 2012, at 08:17, Rich Mellor wrote: Can anyone still read PC formatted 5.25 disks and convert it onto a 3.5 disk? I have a 5 1/4 disk drive. Also PC Conqueror is able to read these disks in PC format. Xover should then be able to produce QL 3 1/4 disks. I will design a tool to add the extra 1/4 diameter (8-)# Tony -- QBBS (QL fido BBS 2:257/67) +44(0)1442-828255 t...@firshman.co.uk http://firshman.co.uk Voice: +44(0)1442-828254 Fax: +44(0)1442-828255 Skype: tonyfirshman TF Services, 29 Longfield Road, TRING, Herts, HP23 4DG ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
Re: [Ql-Users] PC 5.25 Disk
On 18 Feb 2012, at 11:13, Tony Firshman wrote: I will design a tool to add the extra 1/4 diameter (8-)# Can you do it in millimetres? George ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
Re: [Ql-Users] DEBUG
Hi George On Saturday 18 February 2012, 9:56George Gwilt wrote: I use DEBUG 0 and 1 for the same reasons as you and have never had the fault you mention. If you could send me, privately, a copy of your program I'll try to locate the problem. Thanks for your offer of help, this is really appreciated. However, I believe I have solved the problem. I tried moving the piece of code to near the beginning of the program, and this solved the puzzle. My guess is that because my program is over 64k, the DEBUG mechanism could not cope, so that the fault is actually with Turbo. DEBUG must be using unsigned integers, when it should be using floating point variables. That is my guess. The piece of code under question is: 22268 REMark DEBUG 1 22276 DEFine PROCedure how 22284 LOCal p, scan_rt 22292 CLS 2 : PRINT 22300 p = BASIC_L(56) 22308 REPeat scan_rt 22316 p = p + 24 22324 IF p BASIC_L(60)-24 : EXIT scan_rt 22332 IF BASIC_W%(p+18)0 22340 PRINT Call at ;BASIC_W%(p+18); in ; 22348 ELSE 22356 PRINT Stop at ;BASIC_W%(146); in ; 22364 END IF 22372 IF BASIC_W%(p-12) 0 : IF NOT COMPILED : LIST #1; BASIC_W%(p-12) 22380 END REPeat scan_rt 22388 END DEFine how 22396 REMark DEBUG 0 This piece was copied from the Turbo Toolkit Demos file, the original procedure name being How_COME. My idea of using DEBUG was to try and save a little bit of code, because my program is so large. Hi Malcolm On Friday 17 February 2012, 21:35 Malcolm Cadman wrote: Also useful to use and declare integer values, wherever you can, at the start of the BASIC program - which is value% rather than value. Yes, I agree. There is a particular reason for this. Suppose the compiled program stops somewhere with an out of range error. The SuperBASIC version could then be run using the same input data, duplicate the error and stop at exactly same place. The procedure how would then be run to discover the call hierarchies that got the program to that point. Variable values could then be examined with the view to pin-point the cause of the error. However, if using IMPLICIT% value, then the SuperBASIC version would be using floating point variables and the same error would not be produced and so would not stop at the same place. Michael Bulford ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
Re: [Ql-Users] PC 5.25 Disk
George Gwilt wrote: On 18 Feb 2012, at 11:13, Tony Firshman wrote: I will design a tool to add the extra 1/4 diameter (8-)# Can you do it in millimetres? He has to, because unlike a 5 1/2 disc, which really has that size, a 3,5 disc is in reality a 90mm disc. This is only roughly 3,5 inches (3,5433 to be precise). ;-) Marcel ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
Re: [Ql-Users] PC 5.25 Disk
On 18 Feb 2012, at 14:53, Marcel Kilgus wrote: On 18 Feb 2012, at 11:13, Tony Firshman wrote: I will design a tool to add the extra 1/4 diameter (8-)# Can you do it in millimetres? He has to, because unlike a 5 1/2 disc, which really has that size, a 3,5 disc is in reality a 90mm disc. This is only roughly 3,5 inches (3,5433 to be precise). ;-) So both 3.25 and 3.5 are underestimates. George ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
Re: [Ql-Users] PC 5.25 Disk
On 18/02/2012 10:14, George Gwilt wrote: On 18 Feb 2012, at 08:17, Rich Mellor wrote: Can anyone still read PC formatted 5.25 disks and convert it onto a 3.5 disk? I have a 5 1/4 disk drive. Also PC Conqueror is able to read these disks in PC format. Xover should then be able to produce QL 3 1/4 disks. George ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm Hi George, That would be great - I need the programs stored in a format I can get back onto a PC formatted disk that is the only issue... I will send it to you Kind Regards -- Rich Mellor RWAP Services Specialist Enuuk Auction Programming Services www.rwapservices.co.uk ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
[Ql-Users] GST QED Editor
I have managed to rescue a copy of the QC compiler from GST. It uses their own editor, QED, which appears to have been compiled with QC looking at the executable code. However, QED crashes on q-emulator - does anyone have a working copy (or was a ROM needed for QC?) -- Rich Mellor RWAP Services Specialist Enuuk Auction Programming Services www.rwapservices.co.uk ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
Re: [Ql-Users] GST QED Editor
Hi Rich, you'll find all GST written QL software for download on my website. Just follow the link on the Sinclair QL Preservation Project page. I'm out of home now and don't have the URL by hand. Cheers, Urs Von meinem iPhone gesendet Am 18.02.2012 um 21:57 schrieb Rich Mellor r...@rwapservices.co.uk: I have managed to rescue a copy of the QC compiler from GST. It uses their own editor, QED, which appears to have been compiled with QC looking at the executable code. However, QED crashes on q-emulator - does anyone have a working copy (or was a ROM needed for QC?) -- Rich Mellor RWAP Services Specialist Enuuk Auction Programming Services www.rwapservices.co.uk ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
Re: [Ql-Users] GST QED Editor
I've got the GST C compiler. Just tried QED with Q-emulator and it worked just fine. If can't get it off of Urs's site, I can zip it up and send it to you. Tim Swenson ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
Re: [Ql-Users] GST QED Editor
OK - I am downloading it now (75MB for all the GST software !!) Downloads appear on http://www.qlvsjaguar.homepage.bluewin.ch/QL_GST_SW_is_PD.html Dilwyn - can you add the GST programs to the Sinclair QL Homepage (split into different ZIP files!) Rich On 18/02/2012 21:15, ql wrote: Hi Rich, you'll find all GST written QL software for download on my website. Just follow the link on the Sinclair QL Preservation Project page. I'm out of home now and don't have the URL by hand. Cheers, Urs Von meinem iPhone gesendet Am 18.02.2012 um 21:57 schrieb Rich Mellorr...@rwapservices.co.uk: I have managed to rescue a copy of the QC compiler from GST. It uses their own editor, QED, which appears to have been compiled with QC looking at the executable code. However, QED crashes on q-emulator - does anyone have a working copy (or was a ROM needed for QC?) -- Rich Mellor RWAP Services Specialist Enuuk Auction Programming Services www.rwapservices.co.uk ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm -- Rich Mellor RWAP Services Specialist Enuuk Auction Programming Services www.rwapservices.co.uk ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
Re: [Ql-Users] DEBUG
In message 1329572303.66299.yahoomail...@web171520.mail.ir2.yahoo.com, Michael Bulford michaelbulf...@yahoo.co.uk writes Hi George On Saturday 18 February 2012, 9:56George Gwilt wrote: I use DEBUG 0 and 1 for the same reasons as you and have never had the fault you mention. If you could send me, privately, a copy of your program I'll try to locate the problem. Thanks for your offer of help, this is really appreciated. However, I believe I have solved the problem. I tried moving the piece of code to near the beginning of the program, and this solved the puzzle. My guess is that because my program is over 64k, the DEBUG mechanism could not cope, so that the fault is actually with Turbo. DEBUG must be using unsigned integers, when it should be using floating point variables. That is my guess. The piece of code under question is: 22268 REMark DEBUG 1 22276 DEFine PROCedure how 22284 LOCal p, scan_rt 22292 CLS 2 : PRINT 22300 p = BASIC_L(56) 22308 REPeat scan_rt 22316 p = p + 24 22324 IF p BASIC_L(60)-24 : EXIT scan_rt 22332 IF BASIC_W%(p+18)0 22340 PRINT Call at ;BASIC_W%(p+18); in ; 22348 ELSE 22356 PRINT Stop at ;BASIC_W%(146); in ; 22364 END IF 22372 IF BASIC_W%(p-12) 0 : IF NOT COMPILED : LIST #1; BASIC_W%(p-12) 22380 END REPeat scan_rt 22388 END DEFine how 22396 REMark DEBUG 0 This piece was copied from the Turbo Toolkit Demos file, the original procedure name being How_COME. My idea of using DEBUG was to try and save a little bit of code, because my program is so large. Hi Malcolm On Friday 17 February 2012, 21:35 Malcolm Cadman wrote: Also useful to use and declare integer values, wherever you can, at the start of the BASIC program - which is value% rather than value. Yes, I agree. There is a particular reason for this. Suppose the compiled program stops somewhere with an out of range error. The SuperBASIC version could then be run using the same input data, duplicate the error and stop at exactly same place. The procedure how would then be run to discover the call hierarchies that got the program to that point. Variable values could then be examined with the view to pin-point the cause of the error. However, if using IMPLICIT% value, then the SuperBASIC version would be using floating point variables and the same error would not be produced and so would not stop at the same place. Michael Bulford Hi Michael, It is always difficult to understand another persons code. Personally I would look to structure your program more. Your line was 22340 PRINT Call at ;BASIC_W%(p+18); in ; 22348 ELSE PRINT Stop at ;BASIC_W%(146); in ; 22364 END IF 22372 IF BASIC_W%(p-12) 0 : IF NOT COMPILED : LIST #1; BASIC_W%(p-12) Whereas 22340 PRINT Call at ;BASIC_W%(p+18); in ; 22348 ELSE 22356 PRINT Stop at ;BASIC_W%(146); in ; 22364 END IF 22372 IF BASIC_W%(p-12) 0 : IF NOT COMPILED : LIST #1; BASIC_W%(p-12) Is more understandable in its layout. The SELect ON structure is also available, as a clearer alternative to IF ... END IF and ELSE. Which is useful for a complicated series of conditions, and can also incorporate IF and END IF statements. Good luck with program ... :-) -- Malcolm Cadman ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
Re: [Ql-Users] GST QED Editor
Urs, Great job in creating this archive of GST programs and documents. Not only is it useful for those looking to tinker with the software, but also useful in the historical context. More of the QL scene needs to be digitized and archived for future reference. Tim Swenson ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
