Re: [ql-users] MinisQL
On Wed, 7 Feb 2001 at 21:22:23, Dilwyn Jones [EMAIL PROTECTED] .uk wrote: (Ref: 005401c0914c$2f3ddfa0$ef065cc3@default) I had reason to fire up my MinisQL tonight for the first time in a long time. The reason was: I needed an 'old' system. I was trying to copy a disk with CHR$(0) in the filename and of course SMSQE sees this as a DOS disk filename separator or something and gets totally confused finding it on a QL system. OK, no problem, fire up the MinisQL with QDOS to copy and rename the files, then find that the floppy disk drive does not work. The power is getting to it, but no drive light, no files listed (on any floppy disk!). Anyone got any idea what might be wrong - the system is Aurora, Super Gold Card, Qubide 2.1, Mplane... Not that expensive to find a new drive of course, but if anyone has any suggestions to save a few pounds! (The rest of the MinisQL works OK, just can't get the floppy drive to work). I assume you have made sure the ribbon cable is OK? Try pushing the cable in and out to clean the connections (both ends). Does the drive motor start at all? -- QBBS (QL fido BBS 2:257/67) +44(0)1442-828255 mailto:[EMAIL PROTECTED] http://www.firshman.demon.co.uk Voice: +44(0)1442-828254 Fax: +44(0)1442-828255 TF Services, 29 Longfield Road, TRING, Herts, HP23 4DG
Re: [ql-users]GD2 again
Timothy Swenson writes: Isn't there a way to check to see if a Keyword is available? In DJTK there is the CHECK command, that looks to see if a PROC/FN is available. I'm guessing this will work for the GD2 commands, like PALETTE_QL. Have not tried it myself, but it's worth a look. Get DJTK from Dilwyn's page on the Other Sofware page. Its probably the surest way, though somewhat gawky, dont you find? The Thing list is probably the one to use in these situations, but then there doesnt appear to be a GD2 Thing or anything related. An alternative might be to read the mode, though that is a rather indirect way of doing things, and not necessarily unambiguous with regard to the presence of the keyword in question. The keyword is directly related to certain capabilities of the OS, and it is those capabilities that I really want to test for. Are there no new keys in the sys vars to indicate the presence of GD2, like in the display mask (sys_mdsp) ? (Apparently not.) Just tested: Called iow.papp on a pre-colour SMSQ/E (this is the key for the first of the new traps). It didnt return NI, as might be expected, but BP (or is this a genuine BP error from some undocumented trrap?). Still, a utility or keyword to test for this might be a possible solution. Anyone know anything to the contrary? Later: Yes, I do! I wrote a SB keyword as described above. It worked as expected in various pre-colour versions of SMSQ/E, and on 2.98 in hi-colour mode - but not in 2.98 QL-colour mode - there the trap seems to work - ie no errors - although it isnt implemented! :(( Do we call this a "feature" or what? Other suggestions? Per
Re: [ql-users] QPC2v2 again
Exactly the same problem as I reported a week or so ago. GO to SBASIC, enter OPEN#3,PAR and you'll find that seems to flush out the printed output, if it's the same problem as I have with QPC2v2final. -- Dilwyn Jones [EMAIL PROTECTED] http://www.soft.net.uk/dj/index.html Help! I just discovered I cant print from QPC2v2! The old version runs fine, but the new one doesnt talk to the printer (though it had a quick stab at the fax device (using the default setting)). Tried both the new Printer setting, then LPT1 (to which my Epson is connected) - no joy! As I said; the old QPC/SMSQ2.93 worked fine on the default setting. Per
Re: [ql-users] MinisQL
Tony Firshman wrote: I assume you have made sure the ribbon cable is OK? Try pushing the cable in and out to clean the connections (both ends). Does the drive motor start at all? When I switched it on again tonight to do a more thorough test, the drive works in that it gives a dircetory listing of a disk inserted (using both SMSQE and QDOS JM). However, when the disk stops and the drive light goes out, there is a hammerdrill noise from the drive. It sounds rather as though the drive is dying I'm afraid. I've had problems before with internal connections in the MinisQL and this was the first thing I thought of. The room where the computers are stored are not the warmest in the house; I'll try improving the heating a bit for a few days - its problems seem to have always happened during the winter. Bill Waugh suggested that I try putting the CHR$(0) filename in quotes - I have tried this Bill and it doesn't make any difference in this case. The error message I constantly get is End Of File. Time to give up on this one I think until I can get an old level 1 QL out of the attic (it's an old QDOS disk so presumably worked at some time!) -- Dilwyn Jones [EMAIL PROTECTED] http://www.soft.net.uk/dj/index.html -- Dilwyn Jones [EMAIL PROTECTED] http://www.soft.net.uk/dj/index.html
Re: [ql-users]GD2 again
P Witte wrote: Whats the best way for programs to test for GD2? Suggestions for both SBasic and assembler welcome! DISP_TYPE returns 0 for QL mode, 32 for QPC/QXL 16bit and 33 for Q40 16bit. In assembler the same function is available through the display driver thing. Marcel No good for QDOS. I suspect Per wants to give a program a chance to be able to look for GD2 and take appropriate action if not there. DISP_TYPE is only in SMSQE -- Dilwyn Jones [EMAIL PROTECTED] http://www.soft.net.uk/dj/index.html
[ql-users] Wherefor art thou, GoldFire?
With the recent, and not so recent discussions on hardware vs emulators, I decided to update everyone on the status of GoldFire. Especially since my name was pointedly called :-) and I've gotten a few personal mails about it too. Well, folks (yeah, right, now I'm converting into a redneck) the news is that there's really not that much news. Problem 1: Time is short, and money is even shorter (make that VERY short). In fact, I am selling some of my stuff to be able to afford the parts I still need for GoldFire. At this point, I feel I need to get one thing clear - I will not accept any money donations (and I'm saying this because there have been offers). What I will accept is hep at getting some parts, or even the parts themselves. I am still looking for a few samples of the 91C94 or 96, a 144-pin SDRAM SODIMM, M4A3-256/128 CPLDs, and MCF5102PV40 (I only have the 33MHz version), or help at getting them. Also, let me give a small contribution to the developing hardware vs developing software debate: people who have never tried jumping through hoops while bending backwards in order to get the parts they need, at reasonable quantity and reasonable price, will only understand the nerve-wrecking nature of that persuit, when they try it themselves. Problem 2: There is simply no way I can do the work on the initialization software and QDOS/SMSQ modifications involved in getting the GoldFire to work. You see, even when hardware is developed, notning happens if software dose not folow, ar even gets developed side by side, with the hardware. Most of the time spent in designing GoldFire is spent in developing and simulating the programming of the logic chip(s), and even when the simulations run through perfectly, there is no warranty it will work for real. If I have to do the initialization software and the other mods, I might as well forget about the whole project. I would gretly apreciate any help with this. Problem 3: As you can see, it takes years to get something like the GoldFire done because of the above two problems. This of course makes everything much worse - things are not standing still, and everyone has some input on what else should be integrated into a new hardware product. I have gone to great pains to make the design as flexible as possible, to introduce new features (otherwise what would be the point?), but still as compatible with old hardware - all while trying to keep the cost at basically the cost of the parts. This is NOT easy. Unfortunately, this also means that the design itself is really obsolete when it's finished. The MCF 5102 has already been superceeded by two newer CPUs and we can't use it because it's such a problem writing and modifying the necessary software - in fact, it's unlikely that most of the features I've lost a whole lot of time thinking out and designing will ever be used. Yet, on the other hand, people complain about not having the features on the QL they have on the PC. This attitude makes things even more complicated for the developers, as if they were not complicated enough. Contrary to what you may think, no I will not go into the 'why do we need filenames longer than 36 characters' discussion, at this point. But I will be blunt: you can't hold it in and fart at the same time, please excuse my language. Nasta
Re: [ql-users] MinisQL
Dilwyn Jones wrote: Time to give up on this one I think until I can get an old level 1 QL out of the attic (it's an old QDOS disk so presumably worked at some time!) You could use a disc editor like wined, search for the filename and replace the 0 with a valid character. Marcel
Re: [ql-users]GD2 again
Marcel Kilgus writes: DISP_TYPE returns 0 for QL mode, 32 for QPC/QXL 16bit and 33 for Q40 16bit. In assembler the same function is available through the display driver thing. Well, that solves that. Thank you ! :) Perhaps youd care to update the manual: QPC2v2 supplement p13, states just that "..DISP_TYPE always returns 0." so naturally I didnt check. Per
[ql-users] QPC v.2 C68
I posted that before but I got no answer. Here it is again. C68Tool freezes on my QPC v.2 whenever I trie to type ANYTHING in the fields (like make file filename etc... Only the colours options work). It works with QPC 1 and uQLx but not with QPC v.2. Anybody know why. Do you know of any memory limitations? (I have my QPC v.2 set for 128 Megs, I tried also with as low as 4 Megs) Phoebus
