[Ql-Users] Hardware question
I was just wondering what would be involved in burning my own EPROM with my own set of routines for plugging into the ROM port (like TK2), has anyone done this? what sort of kit is involved and how much are we talking about here. Also would I have to make my own pcb or can they be bought/manufactured. This is all for the original QL of course. Lee Privett ¦¦ Sent from my Laptop running XP but emulating the QL using QPC2 ¦¦ ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
Re: [Ql-Users] Hardware question
On 12/02/2011 13:32, Lee Privett wrote: I was just wondering what would be involved in burning my own EPROM with my own set of routines for plugging into the ROM port (like TK2), has anyone done this? what sort of kit is involved and how much are we talking about here. Also would I have to make my own pcb or can they be bought/manufactured. This is all for the original QL of course. Lee Privett ¦¦ Sent from my Laptop running XP but emulating the QL using QPC2 ¦¦ ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm Hi Lee, There is a special header for EPROM code, but I don't have it to hand... I have plenty of spare PCBs however :-) -- Rich Mellor RWAP Services http://www.rwapsoftware.co.uk http://www.rwapservices.co.uk -- Try out our new site: http://sellmyretro.com ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
Re: [Ql-Users] Hardware question
Lee Privett wrote: I was just wondering what would be involved in burning my own EPROM with my own set of routines for plugging into the ROM port (like TK2), has anyone done this? what sort of kit is involved and how much are we talking about here. Also would I have to make my own pcb or can they be bought/manufactured. This is all for the original QL of course. The Technical Manual states: 11.4 Add-on Card ROMs When the machine is booted, the operating system checks for plug-in ROM drivers by looking for the characteristic longword flag $4AFB0001 at the base of each location in which a ROM might be present. The beginning of a plug-in ROM should be in the following format: 00 $4AFB0001 (flag to indicate ROM is present) 04 pointer to list of BASIC procedures and functions 06 pointer to initialisation routine 08 string identifying the ROM The pointers are relative to the base of the ROM. If the list pointer is zero then there will be no attempt to link routines into SuperBASIC. There are also a few tools, which do that for you. There is one from Jochen Merz, very good and easy to use (Thing EPROM-Manager) and one from Liberation Software (RPM-Manager, not do delightful, but working) Cheers...Ralf ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
Re: [Ql-Users] Hardware question
Thanks guys, I am now giving some serious thought to a Retro Arcade Console with the QL at the core, but at switch-on I don't want the user to have to see or press the F1/F2 configuration choice, so the next thing is in the EPROM code (which I assume will run first) can I get it jump passed the F1/F2 choice and just to if F2 has been pressed so that it finishes off the sequence as in TV mode and looks for a boot file or will it just load in extensions from the memory locations in the EPROM? Lee Privett ¦¦ Sent from my Laptop running XP but emulating the QL using QPC2 ¦¦ - Original Message - From: Ralf Reköndt To: ql-us...@q-v-d.com Sent: Saturday, February 12, 2011 2:35 PM Subject: Re: [Ql-Users] Hardware question Lee Privett wrote: I was just wondering what would be involved in burning my own EPROM with my own set of routines for plugging into the ROM port (like TK2), has anyone done this? what sort of kit is involved and how much are we talking about here. Also would I have to make my own pcb or can they be bought/manufactured. This is all for the original QL of course. The Technical Manual states: 11.4 Add-on Card ROMs When the machine is booted, the operating system checks for plug-in ROM drivers by looking for the characteristic longword flag $4AFB0001 at the base of each location in which a ROM might be present. The beginning of a plug-in ROM should be in the following format: 00 $4AFB0001 (flag to indicate ROM is present) 04 pointer to list of BASIC procedures and functions 06 pointer to initialisation routine 08 string identifying the ROM The pointers are relative to the base of the ROM. If the list pointer is zero then there will be no attempt to link routines into SuperBASIC. There are also a few tools, which do that for you. There is one from Jochen Merz, very good and easy to use (Thing EPROM-Manager) and one from Liberation Software (RPM-Manager, not do delightful, but working) Cheers...Ralf ___ 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] Hardware question
Lee Privett wrote, on 12/Feb/11 15:03 | Feb12: Lee/ Thanks guys, I am now giving some serious thought to a Retro Arcade Console with the QL at the core, but at switch-on I don't want the user to have to see or press the F1/F2 configuration choice, so the next thing is in the EPROM code (which I assume will run first) can I get it jump passed the F1/F2 choice and just to if F2 has been pressed so that it finishes off the sequence as in TV mode and looks for a boot file or will it just load in extensions from the memory locations in the EPROM? I don't think so, but Minerva will - at least it shows the F1/F2 but presses F2 after an interval. but not what you want. I bet that though could be patched. The code is open source. Re burning you should look for a second hand QEPIII eprom programmer. It fits in the expansion slot so saves/reads from microdrive. I used an internally expanded QL and Romdisq so bypassed the microdrives. 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] Hardware question
Lee Privett wrote: Thanks guys, I am now giving some serious thought to a Retro Arcade Console with the QL at the core, but at switch-on I don't want the user to have to see or press the F1/F2 configuration choice, so the next thing is in the EPROM code (which I assume will run first) can I get it jump passed the F1/F2 choice and just to if F2 has been pressed so that it finishes off the sequence as in TV mode and looks for a boot file or will it just load in extensions from the memory locations in the EPROM? As far as I know, just Minerva supports an automatic start of the OS after a few seconds. With Jochen's tool, you can also put a SuperBASIC program into the eprom. This will be set as a device BOOT, which the OS searches first. Cheers...Ralf ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
Re: [Ql-Users] Hardware question
I have only ever seen the Minerva ROM in emulation packages, is it an actual ROM I can get hold off and replace the JS/JM type or is it a little more complicated than that? Lee Privett ¦¦ Sent from my Laptop running XP but emulating the QL using QPC2 ¦¦ - Original Message - From: Ralf Reköndt To: ql-us...@q-v-d.com Sent: Saturday, February 12, 2011 3:16 PM Subject: Re: [Ql-Users] Hardware question Lee Privett wrote: Thanks guys, I am now giving some serious thought to a Retro Arcade Console with the QL at the core, but at switch-on I don't want the user to have to see or press the F1/F2 configuration choice, so the next thing is in the EPROM code (which I assume will run first) can I get it jump passed the F1/F2 choice and just to if F2 has been pressed so that it finishes off the sequence as in TV mode and looks for a boot file or will it just load in extensions from the memory locations in the EPROM? As far as I know, just Minerva supports an automatic start of the OS after a few seconds. With Jochen's tool, you can also put a SuperBASIC program into the eprom. This will be set as a device BOOT, which the OS searches first. Cheers...Ralf ___ 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] Hardware question
On 12 Feb 2011, at 15:16, Ralf Reköndt wrote: Lee Privett wrote: Thanks guys, I am now giving some serious thought to a Retro Arcade Console with the QL at the core, but at switch-on I don't want the user to have to see or press the F1/F2 configuration choice, so the next thing is in the EPROM code (which I assume will run first) can I get it jump passed the F1/F2 choice and just to if F2 has been pressed so that it finishes off the sequence as in TV mode and looks for a boot file or will it just load in extensions from the memory locations in the EPROM? As far as I know, just Minerva supports an automatic start of the OS after a few seconds. I thought Super Gold Card and probably Gold Card did this. The F1/F2 choice is just not there (if you have requested that). George ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
Re: [Ql-Users] Hardware question
Lee Privett wrote, on 12/Feb/11 16:31 | Feb12: I have only ever seen the Minerva ROM in emulation packages, is it an actual ROM I can get hold off and replace the JS/JM type or is it a little more complicated than that? It is. There is a small PCB but it would be easy to wire up a pcb to emulate it. Three pins need bending out and reassigning. 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] Hardware question
gdgqler wrote, on 12/Feb/11 16:40 | Feb12: On 12 Feb 2011, at 15:16, Ralf Reköndt wrote: Lee Privett wrote: Thanks guys, I am now giving some serious thought to a Retro Arcade Console with the QL at the core, but at switch-on I don't want the user to have to see or press the F1/F2 configuration choice, so the next thing is in the EPROM code (which I assume will run first) can I get it jump passed the F1/F2 choice and just to if F2 has been pressed so that it finishes off the sequence as in TV mode and looks for a boot file or will it just load in extensions from the memory locations in the EPROM? As far as I know, just Minerva supports an automatic start of the OS after a few seconds. I thought Super Gold Card and probably Gold Card did this. The F1/F2 choice is just not there (if you have requested that). Ah yes you are right, but I think it only 'presses' it - the start screen still appears I believe. I use Minerva so haven't bothered with that for years. 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] Hardware question
On 12 Feb 2011, at 17:06, Tony Firshman wrote: Ah yes you are right, but I think it only 'presses' it - the start screen still appears I believe. As I recall the start screen does not in fact appear. (But that was before the battery gave out!) George ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
Re: [Ql-Users] Hardware question
Op Sat, 12 Feb 2011 17:40:58 +0100 schreef gdgqler gdgq...@gmail.com: I thought Super Gold Card and probably Gold Card did this. The F1/F2 choice is just not there (if you have requested that). The SCG has a few commands that should be used under QDOS or Minerva, before a Boot file is run. AUTO_TK2F1 or AUTO_TK2F2 will invoke Toolkit2 and skip the F1/F2 prompt the next time the machine is booted. This setting is remembered as long as the clock battery has power. AUTO_DIS will disable this automatic booting. Bob -- The BSJR QL software site at: http://members.chello.nl/b.spelten/ql/ ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
Re: [Ql-Users] Hardware question
So I need to look out for a Gc, SGC or Minerva conversion kit, haven't seen those on eBay or sell my retro any other places? Lee Privett ¦¦ Sent from my Laptop running XP but emulating the QL using QPC2 ¦¦ - Original Message - From: gdgqler To: ql-us...@q-v-d.com Sent: Saturday, February 12, 2011 5:15 PM Subject: Re: [Ql-Users] Hardware question On 12 Feb 2011, at 17:06, Tony Firshman wrote: Ah yes you are right, but I think it only 'presses' it - the start screen still appears I believe. As I recall the start screen does not in fact appear. (But that was before the battery gave out!) George ___ 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] Hardware question
In message 4d5690f5.20...@rwapservices.co.uk, Rich Mellor r...@rwapservices.co.uk writes On 12/02/2011 13:32, Lee Privett wrote: I was just wondering what would be involved in burning my own EPROM with my own set of routines for plugging into the ROM port (like TK2), has anyone done this? what sort of kit is involved and how much are we talking about here. Also would I have to make my own pcb or can they be bought/manufactured. This is all for the original QL of course. Lee Privett ¦¦ Sent from my Laptop running XP but emulating the QL using QPC2 ¦¦ ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm Hi Lee, There is a special header for EPROM code, but I don't have it to hand... I have plenty of spare PCBs however :-) I remember the BBC micro have several Sideways ROM pcb's produced, along with software. Which allowed you to switch in to a different set of ROM's. Would that hardware be possible with the QL? -- Malcolm Cadman ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
[Ql-Users] [QL-Musers] OCD things we've done to our QLs...
Hi all, I received a USB floppy drive in the mail today, which will help things along nicely. I just need to find somewhere locally that still sells floppies. However, when I was formatting My First Floppy it reminded me of something I did to my QL back in the Sandy days. I was never satisfied that I usually got 205-209 sectors out of a microdrive cartridge. I wanted more. I often received cartridges with anything from 190 to 222 good sectors! DANG! I wanted the extra 7K or storage. I took off the cover, and ran the microdrives. I just wrote a little program to try to format forever, ignoring any errors. Then, I got the finest nail file my Mum had, and I gently reduced the diameter of the capstan rubber. I did it very evenly and smoothly, and stopped every .002... Sure enough, on testing, each slight reduction got the tape to run just a little slower past the head, and capacity increased. And that's how I got microdrive cartridges that always formatted to 228-230 sectors. I found past about that, the number of format failed responses started to rise dramatically. Also, Mum would start to notice the black rubber all over her expensive emory boards and wonder about me... :) What OCD things have you done to your QL? Dave ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
[Ql-Users] [QL-USAers] USA QLs...
Hi all. I have been looking at my US QL, and noting many differences from UK keyboards. Here's what I have seen so far. The PCB most resembles an Issue 7 board, but with some changes. The first apparent difference is the odd serial and joystick connectors were replaced by standard 9-pin D sockets. The case rear bottom shell was modified so the 4 sockets sit in a metal gasket which plugs the gap. The interior of the top and bottom case were metalised using a vapor deposition technique (the same one used to make toys or CDs shiny). Continuing this theme, a large ferrite ring cuts noise on a pair of wires in the power supply section, tucked under the heatsink. The ROMs are JSU, and are the plastic type. Weirdly, the $ was made in Korea, and the $8000 was made in Mexico. There is a small 2cm x 2.5cm daughter card stuck to the top of the on-board memory with 4 dabs of silicon. There are four wires coming from the board to various points on the PCB. It contains one IC, a 74HCU04B1, two resistors and a disc capacitor. There are a few wires making some changes to the PCB. On the 68008, a wire bridge joins pins 15 and 35. This link is joined via a 22pf cap to pin 13. On the 8301, pin 6 is joined to pins 11, 12, 30, 31 and 32 via five 1n4148 diodes. There are a few other small differences, no greater than the difference between an Iss.5 and Iss.7 board. Photos will be posted at http://www.nonstickglue.com/qlphotos/ in an hour or two. Dave ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
[Ql-Users] Ser-USB Driver Update: External Command Interface (and Progress Update)
Here is a list of the commands that the current version of the Ser-USB Driver can execute through its command pipe interface. This interface supports run-time interrogation and configuration of the driver and is intended to enable the development of utility software that does not require detailed knowledge of the underlying hardware. When the necessary code support is completed there will also be commands for mounting/unmounting partitions. This interface has primarily come about as a result of including run-time debugging so I would be very interested to hear any views on its usefulness, or what other features might be desirable. usbcmd_get_dr_ver $01 Get Driver Version Command Size: Byte Response Size: Long Returns the Ser-USB Driver version as four characters. usbcmd_get_hw_ver $02 Get Hardware Version Command Size: Byte Response Size: Long Returns the hardware (USBWiz) version as four characters. usbcmd_get_hw_type $03 Get Hardware Type Command Size: Byte Response Size: Long Returns the hardware type as four characters. USBWiz returns USBW. Other hardware types are supported as per the original QUBIDE defines (though these are unlikely to be encountered). usbcmd_get_q_stats $04 Get I/O Queue Stats Command Size: Byte Response Size: Long Returns statistics about the I/O Queue as a long word. High word contains the maximum I/O Queue size in requests. Low word contains the current number of entries in the queue. usbcmd_get_io_state $05 Get I/O State Command Size: Byte Response Size: Long Returns information about the currently executing I/O operation. High word contains the op code of the current operation (ip_op_read=1 or io_op_write=2). Low word contains the stage number in the operation. usbcmd_get_flags $06 Get Flags Command Size: Byte Response Size: Long Returns all flag bytes as one long word. High word contains the debug flags in the top 8 bits, the USBWiz flags in the bottom 8. Low word contains 0 in the top 8 bits, the Ser-USB Driver flags in the bottom 8. usbcmd_get_mphys_drv $10 Get Mapped Physical Drive Command Size: Byte with operand in low nibble ($11..$18) Response Size: Long Returns the physical drive/partition that is currently mapped to a USB drive number. High word contains the Logical Unit Number (LUN). Low word contains the partition number. The low nibble of command $10 is a logical drive number in the range 1..8; other values always return 0. usbcmd_clr_flag $e0 Clear Flag Command Size: Byte with operand in low nibble ($e0..$ef) Response Size: Long Clear a Ser-USB Driver or USBWiz flag. Returns the previous state of the flag as 0 or 1. The low nibble of command $e0 is broken down as follows: Bits 0..2 = Flag number (0..7). Bit 3 = 0 for Ser-USB Flags, or 1 for USBWiz Flags. usbcmd_set_flag $f0 Set Flag Command Size: Byte with operand in low nibble ($f0..$ff) Response Size: Long Set a Ser-USB Driver or USBWiz flag. Returns the previous state of the flag as 0 or 1. The low nibble of command $f0 is broken down as follows: Bits 0..2 = Flag number (0..7). Bit 3 = 0 for Ser-USB Flags, or 1 for USBWiz Flags. Here is a tidier version of the example S*BASIC program that I posted in my last mail. It shows how to use the interface in its current form. Requires SMSQ Turbo Toolkit (and the Ser-USB Driver). 100 OPEN #4,NUL 110 OPEN #5,NUL 120 SET_CHANNEL #4,USB_PIPE_W 130 SET_CHANNEL #5,USB_PIPE_R 140 PRINT The Response to Command $01 (Get Driver Version) was: GetResponse$(1) 150 PRINT The Response to Command $02 (Get Hardware Version) was: GetResponse$(2) 160 PRINT The Response to Command $03 (Get Hardware Type) was: GetResponse$(3) 170 PRINT The Response to Command $04 (Get I/O Queue Status) was: GetDWordResponse$(4) 180 PRINT The Response to Command $05 (Get I/O State) was: GetDWordResponse$(5) 190 PRINT The Response to Command $06 (Get Flags) was: Get32BitResponse$(6) 200 PRINT The Response to Command $11 (Get Mapped Physical Drive 1) was: GetDWordResponse$(HEX(11)) 210 REMark === 220 DEFine FuNction GetResponse$(Cmd%) 230 LOCal Response$, This$, Bytes% 240 PRINT #4;CHR$(Cmd%); 250 Response$= 260 Bytes%= 0 270 REPeat GetResponse 280 This$= INKEY$(#5) 290 IF This$ = THEN NEXT GetResponse 300 Response$= Response$ This$ 310 Bytes%= Bytes% + 1 320 IF Bytes% = 4 THEN EXIT GetResponse 330 END REPeat GetResponse 340 RETurn Response$ 350 END DEFine GetResponse$ 360 REMark === 370 DEFine FuNction GetDWordResponse$(Cmd%) 380 LOCal Response$, High%, Low% 390 Response$= GetResponse$(Cmd%) 400 High%= CODE(Response$(1))*256 + CODE(Response$(2)) 410 Low%= CODE(Response$(3))*256 + CODE(Response$(4)) 420 RETurn High% '/' Low% 430 END DEFine GetDWordResponse$ 440 REMark === 450 DEFine FuNction Get32BitResponse$(Cmd%) 460 LOCal Response$, High%, Low% 470 Response$= GetResponse$(Cmd%) 480 High%=
