[ql-users] Test message
This is a test of the emergency broadcast system (or if ntnu.no is still filtering with SPEWS) Dave
Re: [ql-users] Source Code
On Tue, 21 May 2002, Roy Wood replied to something I said: I think this is the way most people would go. Obtain the sources, and use them to gain insight into SMSQ, then reproduce each modular section and release it under the GPL, until the entire OS has been replicated in a GPL'd version. As a half-way step to this, people can accept the distribution side of the license to receive the source, then produce new self-contained replacement modules which they can sell. Nothing in the license prevents someone from making replacement modules. Obviously this is against the intent of the license, but as the code was not submitted to the registrar, it is distributable outside of the original license, as long as the module contains no original SMSQ code and is therefore not a derivitive work Actually no. We have nothing against commercial extensions to the O/S, in fact we would love it to happen. We just want the main code to be uniform as I keep saying. I don't really like patches but you can LRESPR code into SMSQ/E and you can add your own modules. If we can sell these modules we would be very happy to do it and if the people want to give them away the same applies. Roy, you use phrases like commercial extensions, add your own modules etc. I am not talking about that, and know that can happen in a healthy way under this license. What I am talking about is *replacing* modules, using the source to create/reverse engineer an Open Source version of SMSQ. At what point does work product stop being derivitive code and start being clean, unlicensed code? Basically, any module that doesn't include any original SMSQ code fits that requirement. The task of rewriting an OS is not trivial, but with the source, it's certainly a lot easier. The point is that people can write new modules that carry out *existing* module functionality, and distribute those, which actually increases the fragmentation of SMSQ in a way that the registrar is unable to control, because they would have no legal basis to do so. Even TT can't stop people writing replacement sections of SMSQ. It's human nature - I am certain beyond all doubt that there will be a thriving development scene for SMSQ, and 90% of it will be beyond the reach and control of the registrar. It would be in the majority of developer's interest NOT to contribute their efforts, but to simply pad out what is required and do a fee-based (not commercial, but fee-based, as in resellers are not doing this commercially, but fee-based, think about it ;) Finally, I would like to say, as a moderate critic, that if you doubt my intentions, I would like you to consider my thinking for a brief moment. One who truly cares about the future of the scene will care greatly about what form this license takes. Those who do not care, or to whom the license is irrelevant, will remain silent. If I were a less honourable person, I would not point out the obvious flaws and weaknesses, or jump through the holes. I would leave them as wide open as possible and wait until they're adopted. People may be critical, but that is a positive thing if someone's motives are to improve the license for everyone's sake. It's when a person tries to change the license for their own benefit, or stays mysteriously quiet that you have to worry. Yours constructively Dave
Re: [ql-users] Source Code
On Wed, 22 May 2002, Roy Wood wrote: Yes but it is not your concern as a reseller. I agree that we do not want to lose any contribution but some people will not contribute because they have already fixed an attitude which is against what we are doing. This has always been the way of things. Criticism of this license is not criticism of you, or Jochen, or anyone else involved in drafting it. It is a work which you hopefully consider to be a work in progress. If you feel it should stand as it is, that's ok. If it is adopted as is, people will walk elephants through the holes - let's close those holes and make the letter match the intent? The licence does not exclude a developer writing some code that can be added to SMSQ/E as a module and which can be charged for as far as I know. The license only specifies one mechanism for having code added to the official SMSQ tree - to surrender the right to charge for it, remove it, etc. If someone wishes to charge for a module, they are not given an avenue to do so under the current wording, unless they keep their module separate from the SMSQ binary distribution, which ensures marginal adoption at best, and certainly encourages commercial developers to further fragment the code base. [snip large paragraph about why I know this is true from personal experience] [snip rest of my latest comments, for being philosophical and not really pertinant to the issue at hand] And maybe other people might like to exercise a little self-censorship too, in the hope that we may lift this vital discussion up to a higher level, where good things happen? Dave
Re: [ql-users] Source Code
Timothy, I think that the Reference Guide was a document that Jochen put together - and therefore belongs to him from a copyright point of view? Has anyone approached Jochen about the Reference Guide? Having said that you have an excellent point in that nobody has been saying anything about the documentation side of things.I doubt whether Jochen makes any money from it and does it mainly as a service to the community. I know he has had problems keeping it up-to-date. Certainly if the SMSQ/E documentataion could be treated as a communual effort and also if it could be distributed electronically (albeit in what format would need agreeing) I think it would be much easier to keep it up-to-date. This will become more of an issue of authors start making all the extensions to SMSQ/E that we are hoping would happen. If it matters I could supply a secure web site for hosting such items. Coming back to the original source code license, there has been a lot of discussion about only sending the source via physical media. I agree very strongly with others comments that this seems a needless restriction. It seems to add cost and inconvenience for very little gain. It is very easy to provide a secure web site that only allows authorised users to download any file(s) - and also records every such download if that matters! If necessary such a site could be partitioned so that there were different levels of security around different files. Dave - Original Message - From: Timothy Swenson [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Sunday, May 19, 2002 6:08 AM Subject: Re: [ql-users] Source Code I've glanced over the comments made by others on the SMSQ/E official statement and have decided to take a nice long look at the statement myself. The comments below are strictly my opinion, not based on any input from the other commentors. At 02:50 PM 5/13/2002 +0200, you wrote: Official statement == 3/ No distribution of SMSQ/E may be SOLD, except for the official distribution. This interdiction includes that of including and distributing SMSQ/E in Public domain libraries. Official distributions will be sold in compiled (binary) form, possibly together with the official distribution as source code. For such sales, for the time being, two distributors/resellers, namely Jochen MERZ (JMS) and Roy WOOD (QBRANCH) have been appointed by the copyright holder. Resellers provide support for the versions sold by them. Except by prior agreement, binary, i.e. compiled, versions of SMSQ/E may not be distributed other than through the distributors. It would be better to leave out stating who the official distributors are in this Official Statement, and put it in a separate document. It would be kind of like putting in the name of the Officers in a set of By-Laws, as the names will change over time, and the By-Laws probably will not. 4/ The registrar, i.e. me, will maintain official distributions of SMSQ/E, in binary and source code form, one for each machine on which SMSQ/E may run. I would recommend defining the terms Registrar (but not as me) and Distributor/Reseller. Just to fully clarify who they are and what they do. 5/ Any person may make any changes/additions/modifications/adaptions to the source code he feels like. Any person may give away to others the modification he thus made, including the official distribution in source code form only, provided this is made ENTIRELY FOR FREE - no charges, not even copying charges, or charges for the media on which this is distributed, may be levied. I understand the total avoidance of any one making money off of the source code for SMSQ/E, but I feel not allowing charges for media a bit strict. A simple workaround would be to send the person a blank CD or other disk and some IRC's. I am assuming that IRC's are not considered a form of currency. If your local Post Office does not know that an IRC is, then talk directly to the Post Master for that Office. There is no reason for a Postal Employee to not know their job. I spent 8.5 years as a federal employee, so I know the power of the chain of command. This distribution of the source code including the changes/additions/modifications/adaptions made by any author may not be made in electronic form other than on a physical disk. I really don't understand not allowing distribution via anything other than sneaker-net. What would be the consequences of the Registrar, putting the Official Distribution Source Code of SMSQ/E on a web server? It could be arranged that the requester must give their name and address before getting the Source Code. As someone that is about 5,000 miles from the Registrar, mail can take an awfully long time. Plus, someone like Thierry, sitting on a French Naval ship in the Persian Gulf, mail is very slow to come. As a veteran I try to keep fellow service members in mind. Distribution
Re: [ql-developers] Re: [ql-users] Source Code
Timothy, When I got SMSQ/E from Jochen, I got: a) A generic SMSQ/E User Guide (38 pages) that was not machine specific b) Custom supplement pages for each hardware environment I bought (typically 6-10 pages) I agree that the SMSQ/E Reference manual is extra - but I do not think that is what was being refrred to. Dave - Original Message - From: Timothy Swenson [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Sunday, May 19, 2002 4:59 AM Subject: Re: [ql-developers] Re: [ql-users] Source Code At 01:43 AM 5/19/2002 +0100, Roy Wood wrote: What rights are they ? As I have said we have no objections to you becoming an official reseller if you follow the rules. In fact we would be glad if you did because we have no wish to be involved with support for the Q40/Q60. As an official reseller you can sell SMSQ/E for whatever you want provided you pay the fee to TT, provide a printed manual, disk and support for the platforms that you sell.It really is that simple. Printed Manual When I got SMSQ/E I did not get a full printed manual. I got a hardware guide and a very short guide to SMSQ/E for the Q40 (bought mine 2 years ago). The Reference Manual was extra. If I had not know much about QDOS and SMSQ/E when I got the Q40, the manual would not have kept me from being SOL. The Gold Card manual was much more in depth than the SMSQ/E manual I got. Tim Swenson
[ql-users] Booo!
Boo! B I say! Yes, my vacation is over, and now I must return to my desk... Still, it does also mean I can chat with you guys :o) Dave http://ql.spodmail.com/
Re: [ql-users] Source Code
On Mon, 13 May 2002 [EMAIL PROTECTED] wrote: The future licence-to-be has been a bit modified, notably to take into account the fact that test versions must be easily distributed. Here is the (still provisional) text. As usual, I invite all of you to comment. Ok :o) 2/ SMSQ/E will be made available, as source code only, to any person who so requests it. The request must be made to the registrar, i.e. me. The source code will be sent via CD ROM, thus the request must be accompanied by 3 IRCs, else it will be ignored. Never say things likje 'the registrar, i.e. me.' because this means me is the registrar. This is very open to abuse. You would here put a personal or organisation name and contact details. Obviously this is a draft, but this does need correcting. You went on to say: 2/ Authors making additions etc are still prohibited from distributing binary versions of SMSQ/E, even for free. That's not what the license says: 8/ For testing purposes only, authors having made one or several changes/additions/modifications/adaptions of SMSQ/E may, as an exception to the prohibition of distributing code stemming from the official release version in binary form as mentioned above, give away binary version of their code, together with binary versions of SMSQ/E, to not more than 10 persons in total (whatever the number of test versions), provided that the persons receiving these test versions agree to destroy them: - after a period of 2 months, or - at the time the changes/additions/modifications/adaptions for the test version are included in the official release version, or - when they are notified by the author that a stable version is now available whatever comes first. There. Software developers are explicitly allowed to distribute beta/test versions as listed above. However, the way this is currently structured is open to abuse. May I suggest a small change here? Limit distribution of beta/test versions to only those who a) are already entitled by license to posess a copy and b) are actively involved in testing or debugging the software. This will allow genuine distribution, but prevent distribution on a friendly basis. Finally, I strongly advise a change to the structure of the document now that the content is almost there ;o) I would recommend defining Licensor, Licensed Distributor, Licensed Developer and Licensed User as all have different rights and restrictions placed on them by the above license. If you would like, I would be happy to assist you privately to do this, without changing either the intent or the specifics of the license as it now stands... Dave
RE: [ql-users] ROM versions
On Thu, 2 May 2002, Norman Dunbar wrote: This may be true Dave, but you should see the Scottish, Welsh and Irish Well, the Scots don't like the expense of a deflection circuit, so the picture's usually small ;) The Welsh, well, their picture tends to roll up and down, and it's kind of fuzzy! The Irish picture? They haven't managed to fix that for hundreds of years, despite marathon talks by TV engineers! Umm, what happeened to spodmail then ? I was just throwing some Xenu stuff at y'all to make sure you were all immunized ;) Dave http://ql.spodmail.com/
RE: [ql-users] ROM versions
On Thu, 2 May 2002, Norman Dunbar wrote: Well, the Scots don't like the expense of a deflection circuit, so the picture's usually small ;) Don't forget who invented it in the first place though :o) (I suspect, as with all smugness, I shal regret that sentence !) According to the American history books (the ones that almost had me arrested for disagreeing with a teacher in a gas station that John Crapper invented the toilet) Logie Baird, noted American traveller, did it ;) (The teacher said to a friend John Crapper invented the toilet, and I corrected her by saying it was Thomas Crapper, and he didn't invent it, he just patented a toilet flush mechanism he probably didn't invent, and she called the police, and they almost arrested me when I commented that America invented stupidity... That is the sum of my experience with the US educational system, and already I know my children will be educated in England.) Dave http://ql.spodmail.com/
RE: [ql-users] ROM versions
On Thu, 2 May 2002, Norman Dunbar wrote: And, they don't have any QLs anywhere nowadays. (hopeless attempt to get on topic) Yes. If I ever get to twist Nasta's arm to do it (which won't be for a while as he's got more important things to do) I think the BBC was the perfect education machine - it had usable programming language, deep access to the machine (inline assembly, etc) and ports for everything. I really think a QL could do the job better, if it was designed right, and had programmable IO ports and a cleaned up (IE completely redefined to look like it belongs in this century) windowing system. Maybe I'd better sign up to QL Chat :o) Indeed :o) PS. The Americans *did* invent Condensed Milk. Well of course - it has the words con, dense and edmilk in it ;) No, I'm not being down on Americans, but not everything in America is perfect... Still pretty good though :o) Dave
RE: [ql-users] ROM versions
On Thu, 2 May 2002, Norman Dunbar wrote: Been there, done that authorised ! For those not in the know, ql-chat is a mailing list where off-topic chat isn't frowned upon - in fact, it's thoroughly encouraged. Imagine going to the pub, downing a few jars, then going home and trying to write an email. You'll have moments of incisive wit and clarity that are just unreproducible in any other list (and would also probably have you declared a fool, detained for your own protection and made to write a paper on The Quantum Mechanical Theories of Norman Dunbar) To subscribe, send an email to [EMAIL PROTECTED] with subscribe ql-chat in the BODY of the message. You will receive a verification email - simply follow the instructions. Dave Quantum Mechanic
Re: [ql-users] Latest QL-Toady ;-)
On Thu, 2 May 2002, Phoebus Dokos wrote: Hmmm just got my hands on the latest QL Today (renewal form's on the way Jochen, together with the Ad ;-) and I only have one remark for Roy ;-) You know that scene in Airplane! where people queue up to beat the panicking old lady? True in QL-Toady fashion, not only (once more) you made a Roman out of me (DokUs instead of Dokos ;-) but also reversed my first name to Pheobus instead of Phoebus ;-) And I'm always David Parks instead of Dave Park :o) I'm next, and I want to beat whoever with a big, wet haddock! Dave http://ql.spodmail.com/
Re: [ql-users] ROM versions
On Wed, 1 May 2002, Robert Newson wrote: Al Feng wrote: Essentially, when you swap QL ROMs, the video output for TV mode changes from NTSC to PAL and vice-versa for JSU JS, respectively. Errm...don't the ROMs contain the CPU instructions...the video output is shurely the job of other board chips (ZX8301, etc). However, (these are speculation/vague memories [of rumours?]) the screen shape is different(?) and so the drawing routines would be modified (so a CIRCLE is still a circle). Also, would the interrupt routine be running at 60Hz as opposed to 50Hz, and so some timing routines would have been rewritten? I suspect you're both right and both wrong. A US QL with US timings would have problems drawing a UK-resolution screen in the reduced time - I imagine the machine would slow down greatly. Similarly, I suspect a UK QL with US ROMs would speed up slightly. (Slower scan rate AND less to scan) The question is based one xperimenting I'm doing with my US QL. Nasta may want to jump in, but I am also wondering what kind of headroom the original QL mobos have for 'overclocking', in the sense of maybe adding a faster clocked 68008FN at 10-12MHz. I think the on-board RAM would definitely fail at those speds and may have to be removed/neutered ;) Finally, I'm thinking of putting up a web-based survey form asking what systems people use, so I can get an idea of the proportions of different system types out there. The results would help traders aim products at the right group of people (ok, at the expense of the hapless minority still using their original QLs with SPEM memory and DiRen kbd interfaces, who do all their programming in Forth ;) Dave http://ql.spodmail.com/
Re: [ql-users] ROM versions
On Wed, 1 May 2002, ZN wrote: The EU and US specs are actually remarkably similar, and only really differ in the number of lines drawn on the screen. 312 EU, 262 US. However, both However, the English PAL system is BETTER! ;P If you watch US TV for too long, you go blind, and I'm not referring to the lousy programming either ;P To summarise: nothing to spectacular would happen if the ROMs were exchanged. Ow... I was hoping for a rift in the space-time continuum. (I just wanted to know if there was a good reason not to do this, like timings going out and things getting hot or corrupted or etc) Actually, it's the 8301 that limits things. The system will stop working due to read data from the on-board RAM not appearing at the correct time over about 9MHz IIRC - I used to run my QL faster using a separate What if the onboard RAM has been disarmed, and there is faster memory in its place? And there was a 5lb heatsink on the 8301 ;) Dave http://www.xenu.net/
Re: [ql-users] ROM versions
In reply to the comment about a 5 lb heatsink on the 8301, Phoebus studiously and wittily remarked: Then you would probably break the mainboard ;-) Don't forget it's a Sinclair Design not Nasta's ;-) Ahhh, so THAT'S why his designs are all so small and pokey, with the chips practically touching each other! Small board = less leverage. :o) But then again, I have some small boards coming up too :o) Dave
Re: [ql-users] Di-ren Keyboard interface
On Mon, 29 Apr 2002 [EMAIL PROTECTED] wrote: Does anyone have a copy of the manual and disk supplied with the di-ren keyboard interface they could let me have please (photocopy or disk copy of manual acceptable). Is this anything to do with the Di-Ren interface you're selling on eBay? :o) Dave
[ql-users] ROM versions
Hi all, What do you think would happen if you put JS ROMs in a US spec QL? Or JSU ROMs in a UK spec QL? Dave
Re: [ql-users] memory expansion standard ql
On Tue, 30 Apr 2002, paulholm wrote: The boards I have also provide a battery to hold clock time between power cycles, works most all the time. I'm interested in how that works. Do you have any details? Dave
[ql-users] How many...
Just asking for a complete guess here. How many Q40s and Q60s do you all think are out there in customer's hands? Dave
Re: [ql-users] QeyMail question...
On Tue, 23 Apr 2002, Dilwyn Jones wrote: the ability to accept PLAIN TEXT messages only. Maybe a bit contentious, but plain text *is* teh standard for emails - unlike what Little Willy Gates seems to think. Agreed. Agreed, but also not true. The RFCs show that the content type should be included in the header, and may be anything, however the base email should be sent as text with the alternative content as an attachment to be handled by the recipient's mailer. What I propose is a compromise that suits most people: Emails will always be sent plain text. Emails will be received and parsed based on the content-type, so if it's HTML we can strip the tags, and if it's XML likewise but with a different filter rule. By having a plugin filter rule system, we can also direct emails that contain this is not spam, !! and insert offensive words here can be directed straight to hell... The ability to delete messages from the server before downloading them, based on a regular expression, so I can bin all the cr4p fromo *.hotmail.com etc. Agreed even more. In my case, I want to be able to refuse download of files greater than a given file size (e.g. at peak telephone call I think a good solution here is to have two modes of operation: online and offline - online, it will simply get sender/size and if you want to view the message it will download the body. Offline mode, it will connect and fetch all messages and delete them from the server. You cvan then read them offline. Dave http://ql.spodmail.com/
RE: [ql-users] QeyMail question...
On Tue, 23 Apr 2002 [EMAIL PROTECTED] wrote: How about support for both POP3 and IMAP? POP3 support is trivial, and I have all the RFCs here. I don't have documentation for, and have never personally used, IMAP, so it will come second, but it will come. The real intention behind this project is to do a simple, general purpose email client that is easy to use and has some range of configuration and flexibility. Dave
[ql-users] QeyMail question...
Hi all, I'd like to promote a discussion about the features of a QL-based email program. I don't want to discuss standard features just yet, but those exotic features that will really help us. For example, I've recently learned of the difficulty of moving files between machines. Headers are a wonderful thing. Would you prefer to have zip file attachments that are MIME encoded, or a proprietary attachment system that will allow you to transfer files with header info? (I would open up the source of this to anyone wanting to write an FTP client too) What kind of features not already in common use would give a QL email client higher utility value? PS: Making more progress on Qeyboard - look ofr an announcement soon :o) Dave
Re: [ql-users] QeyMail question...
On Mon, 22 Apr 2002, Michael Grunditz wrote: Email using tcp/ip ? Do you have a working stack ? Well, tricky answer. SOQL, but this is all development work for the EtherIDE interface I'm helping Nasta with. We'll be sending out a couple of prototypes to people who are working on TCP/IP so we can hopefully have some working net functionality when it gets a general release... I am interseted to help you in writing tcp/ip clients, or an alternative to tcp/ip. UUCP ?:) Excellent. I would like to have a few people working together with the code accessible to developers - also making it modular so we can reuse blocks in things like telnet, FTP, and maybe a text html parsing procedure... etc etc Less features:-) Well, less is more. Clive taught me that. No, but maybe strict coloring , when commenting like this. Ok, noted. Dave
Re: [ql-users] Re: QBOX-USA
On Mon, 22 Apr 2002, John Impellizzeri wrote: So I decided to shut it down and cancel the phone line, the extra $30 a month will be put to good use. I think it had a good run and was definitely very heavily used for a few years. We started it around September 1993 with '94 - '97 probably it's peak years. I have no regrets running it as long as we did but I think it's time has come and gone. These are critical moments in history, when information is preserved or lost forever. You may have many unique files help nowhere else. Would it be possible for you to archive the whole thing and make it available for a small fee, or send a copy to a couple of the people running PD libraries so they can see what fills gaps in their collection? Also, maybe it is possible to do a superBBS on the web, combining all the files of all the BBS out there? This again for archiving purposes... Just a thought... (all lonely and scared by the isolation, I assure you!) Dave
Re: [ql-users] Re: QBOX-USA
On Mon, 22 Apr 2002, Phoebus Dokos wrote: life and hobbies many times take too much time out of it. Nonetheless with a fully functional TCP/IP very soon now, Websites like the SMS repository I just spat coffee all over my monitor and desk. I just read that last bit as SM suppository... The co-workers are prairiedoggin me :*) Dave http://ql.spodmail.com/
Re: [ql-users] QeyMail question...
On Mon, 22 Apr 2002, Tony Firshman wrote: Well, less is more. Clive taught me that. ... but it is 'fewer' Amazing the way English (and American I think) has lost good English from Tony Blair through the BBC to schools. people, features, bricks (discreet - ie countable) - many. fewer sand, flour, water (not-countable) - much, less OK it is good that language evolves, but losing a subtlety of meaning like this using existing words in the wrong context is bad. NOT your fault Michael - you are in very good and numerous company (8-(# Michael never said that. It was me. My grammer has never been the best, as these sentences show ;) Actually, it was my Mother who always said One less is one more, and made me sensitive to the less is more which even turned up in Shakespeare some place... My English teacher challenged me on it, and, while the subtlety is lost on me, I defeated her with the argument that less and more are singular. Fewer and more are plural. As the saying is a corruption of one less is one more, which came from a discussion of places at dinner (I *think* it was one less (person) is one more (potato)) but the origins are hazy - and I'm just not old enough to have been around at the time. Still, as a Brit in Merika, 'tis my job to be quirky, like a bad cliched stereotype of myself :) I always knew my perfect brummie, cockney and estuary accents would come in handy. Working on pudlian and welsh as we speak :o) Dave PS: I am about to release the YALL version of QDOS, which is in the 'suthun' accent ;)
Re: [ql-users] QeyMail question...
On Tue, 23 Apr 2002, Tony Firshman wrote: Sorry to lead you into a false confession (8-)# It wasn't false! It was entirely genuine! But it's not true about me and that sheep! ;) Dave
Re: [ql-users] c68 question
There is no standard way to get a file re-directed to be treated as a command line in c68. You can do file level re-direction and then process the input as though it comes from stdin. The standard c68 start-up code will handle attaching the input as stdin, but the processing of this input so that it can be an alternative to the command line has to be implemented within the program itself and is not a standard feature of the c68 start-up code. The main reason that this is not done is simply because there is no agreed syntax that specifies the parameters for a command line are coming from a file. It would be relatively trivial to enhance the C68 start-up code to implement such a feature given an agreement on the syntax for recognising the command line re-direction to a file for parameters. The idea sounds like a good one, so if anyone has suggestions on a proposed syntax I am happy to consider them for inclusion into the standard c68 build. Is there any standard for this in the Posix/Unix world as I have not come across such a feature? What about other OS? Dave - Original Message - From: P Witte [EMAIL PROTECTED] To: ql users mailing list [EMAIL PROTECTED] Sent: Saturday, April 20, 2002 10:28 PM Subject: [ql-users] c68 question Is there a way to get a c68 program to accept a commandline (or part of a command line) from a file/pipe. I want to achieve something like: EX cprog ; -options parameters filelist_file rather than EX cprog ; -options parameters file1 file2 .. fileN Or is all this entirely up to cprog? Per
Re: [ql-users] gccDhrystone 2.1
On Sat, 20 Apr 2002, ZN wrote: Assuming you meant 'Nasta', well, it's a nightmare (nocturnal female horse?) Everyone knows if you assume, you make an ass out of u and me, but what that has to do with nocturnal female horses, nightmares, or Natsa the Dr Evil version of Nasta, I have no idea... even describing everything that's involved, AND it would be a post too long even for me. That should be enough for anyone :-) Suffice it to say that PCI cards are hard to do. Lots of things going on that are more-or-less transparent to the OS. But the chipset and card know a about it, oh yes... Dave
Re: [ql-users] Wee_Haa... Got a QXL!
It has always been a limitation of the QXL version of SMSQ(/E) that the QXL.WIN files used both ahrd coded file names and hard coded drives that were not configurable. There is a way around this in that you can use the SUSBST command to assign directories under DOS to drive letters. Then if you keep eaqch QXL.WIN file in its own directory you will satisfy your requirement.Under Windows NT/W2K/XP class systems you can do a similar thing by sharing out a directory and then mapping a directory via the network (it is perfectly permissable to do this back to the same machine). This works fine if you only have a single partition on your machine (i.e. you drive letters are free). Dave - Original Message - From: Phoebus Dokos [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, April 20, 2002 1:25 AM Subject: Re: [ql-users] Wee_Haa... Got a QXL! At 07:58 ìì 19/4/2002, you wrote: Phoebus Dokos wrote: I was wondering if anyone knows (Marcel probably :-) how you can attach other QXL.WIN files apart from the one you can make. Put WIN1 in C:\QXL.WIN, WIN2 in D:\QXL.WIN etc. Yes I know that (and I did), but I was asking if you can assign a .win file (any QXL.WIN file, regardless of filename or disk - a la QPC :-). I have a 20 Giger drive here and it seems pretty stupid to have to partition the drive in order to get Win2_ Phoebus
Re: [ql-users] Repackage tosforql
Michael, You can always get the file in ZIP format from my web site. The download link is http://www.itimpi.freeserve.co.uk/ql/tosforql.zip Dave From: Michael Grunditz [EMAIL PROTECTED] Date: Fri 08/Mar/2002 23:33 GMT To: [EMAIL PROTECTED] Subject: [ql-users] Repackage tosforql Hi I need help to unpack the tostoql.lzh file , because I cant do it..(?). If anyone needs qdos-gcc for AIX , I have fiddled with the source and now it compiles fine. Regards Michael Grunditz ___ Never pay another Internet phone bill! Freeserve AnyTime, for all the Internet access you want, day and night, only £12.99 per month. Sign-up at http://www.freeserve.com/time/anytime
Re: [ql-users] Membranes
On Sun, 10 Mar 2002, Al Feng wrote: The significant problem [which *I* found] is the SHAPE of the top of the QL's tiles ... if you are a moderately fast typist, you are not looking at the tiles AND your fingers are not locked onto the tiles, either; so, you will inevitably be striking the top edges of the cupped portion ... or, at least, I was doing so. It's understandable. We are all individuals. SRL did not design the keyboard. Absolutely not. The key-caps are, in fact, part of a standard system which existed from ~1975 for making short run keyboards. I certainly used an ICL minicomputer with the same style and construction keyboard, in around 1981-2. I also used a late Datacom terminal with exactly the same kbd construction. SRL probably did it that way because they could get it manufactured very cheaply - they would not have to pay for custom 2-shot key mouldings etc. And, of course, the membrane would have been cheaper than a PCB and switches. The membrane replacement prototypes are coming along nicely. Hopefully, next week I shall be in a position to take som pix and put them on my web site. Dave ql.spodmail.com
Re: [ql-users] Q60
On Sun, 10 Mar 2002, Thierry Godefroy wrote: This is a problem with my ISP, I don't know why but all my web sites are currently unavailable on free.fr. I sent email to the support about 1à days ago and I'm still waiting for a reply... I guess one of their server upgrade went wrong... I am happy to mirror your site for US users. If you're interested let me know... Dave
Re: [ql-users] Membranes
On Sat, 9 Mar 2002, Wolfgang Lenerz wrote: If you're going to invest several thousand dollars in a Ql project, my advice would be: don't. (unless you don't care to get'em back) That's why I'm calling it a 'project' and not a 'business' ;) Anyway, as far as a membrane project is concerned, somebody has to do it. There are maybe only 200 - 300 people in the world using their QLs for 'Real Work'... But those 200 - 300 people will have membranes fail in the next few years, and will need to continue somehow. Some will choose external keyboards, some will replace the membrane. So I'm planning to make 100. I won't invest all the money at once. Most of the investment is on a per-board basis, so I won't lose too much in one go. Dave
Re: [ql-users] Membranes
On Fri, 8 Mar 2002, Al Feng wrote: Speculation about the material used in the QL's membranes by Sinclair or otherwise seems futile. I disagree. Here's why. They fail. We have to produce something that does the same function. We don't want it to fail the same way. It is worth noting, IMO, that the reason that the membranes have failed in the past, and will probably fail in the future in a standard QL configuration IS singularly BECAUSE of the proximity to the heatsink. The heatsink is at the opposite end of the QL, and if you put smoke into a QL you'll see it is drawn in at the expansion end, drifts slowly to the heatsink end, then accelerates rapidly and comes out of the grille at the back of the heatsink. Think about it. I have, for a couple of weeks now, full time. :o) As long as the standard PS configuration is used, you are baking the tails. The rest of the keyboard membrane does not appear to suffer from the problem of becoming brittle. The baking is what causes the pthalates to evaporate. The heat comes from components on the board. If you want to make a BETTER *membrane*, then get hold of a TS-2068 and see how Timex made their keyboard -- printed circuit, carbon pads to close the circuit, ribbon wire tails attached to a connector. These are approx 3mm deeper than the current design. I am experimenting with them. They work very well and are durable. I'm just waiting for a better selection of expansion cards to check clearances, etc... Worrying about the pressure needed to actuate a key is a silly exercise if you are simply trying to create a replica of the original membrane because your keyboard membrane's tails will inevitably suffer the same fate which the original membranes experienced ... Worrying about the key pressure is very important. Part of the total key pressure required comes from the inertia of the keycap, to accelerate it down (about 5%), part comes from the rubber bubble mat (about 60%), and part comes from the membrane itself (about 35%). If it requires 1 unit of pressure to press the key, and I produce a membrane that requires, say, double the pressure to operate, it requires a pressure of 1.35 units. This different will be enough to throw off most fast typists, and if you've been using a keyboard for 18 years, the last thing you want is for its characteristics to change. It's a small bit of effort to make a permanent quality product that will last forever and not have any negative side effects. After experimenting with the QL I have here, and checking specifications for a type of kbd that uses the exact same construction as the QL and OPD, I can report that the force specified is 2-3 Newtons. The force actually required increases as the keyboard ages, because the bubblemat and membrane top layer become slightly stiffer. If I am going to invest several thousand dollars in a project, I am going to make sure I understand 100% all the issues involved with my designs, and with the design decisions of the original membrane. Only by understanding the specifications and requirements for performance will I make something that is *perfect* :o) If I can see a way to make this work, every membrane will be stamped with a Born on date, so people can tell how old it is. Dave ql.spodmail.com
Re: [ql-users] Membranes
On Fri, 8 Mar 2002, Tony Firshman wrote: 1) Keybounce. They produced a replacement 8749 to 'cure' this, which it did. Unfortunately it killed ser2 (8-(# Hermes/superHermes have cured key bounce with all keyboards using the pcb connectors. 2) The pcb was sub-standard, and the 'gold' plated contacts weren't. After maybe 5 years, all the contacts need cleaning - quite a major dis/re-assembly job There's a lot of incentive to have poor or false gold contacts - having a large PCB like that plated will more than triple the cost of the PCB. I'm looking for a way to do quality 24K gold plating in-house - it looks like it will cost a few hundred dollars to buy the equipment, and a couple of days practice and training to learn how to use the equipment properly. 3) The ribbon cable was soldered each end, and fractured very easily My design will not have soldered ribbons. It will have IDC cable and connectors, for simple re-usability. 4) The thin pcbs weren't thin enough and ruined the connectors for std membranes The trick to this was to stick a couple of layers of tape to the back of the ribbons to make them thicker. However, my design will have thin pins which enter the two sockets. Careful with your design (8-)# Well, designs. I have three different designs on the go. The one which looks to be technically most robust(40%), subjectively most comfortable (30%) and economically most viable (30%) will be the one that gets produced. Unfortunately, none of them are completely straightforward, from the component manufacturing or availability standpoint. Dave ql.spodmail.com
[ql-users] Membranes
I've been doing some 'research' into the membrane situation for a few weeks, working out the situation with membranes... It turns out they use a plasticiser called DEHP, which is a pthalate. Pthalates are carcinogenic, and they leach out of products. Don't worry, you'd have to suck on a HUGE amount of plastic for a VERY long time for an even measurable amount to be absorbed. Anyway, these pthalates soften the plastic to make it more pliable or rubbery. Membranes need to be a little flexible, but not 'rubbery' so that they eventually distort and take the permanent deformed shape (so keys stick on, etc). Pthalates tend to evapourate. The plastics usually become harder and, if a small amount of pthalates were used the plastic becomes brittle and cracks. Ahah... I am looking at materials and methods to make replacement membranes. If anyone has any knowledge, information, ideas or suggestions, can they please email me? This could include materials, design alternatives, possible sources of materials, manufacturers with short run membrane experience, etc... Thanks... Dave ql.spodmail.com
Re: [ql-users] Membranes
In reply to my own post, I have one particular question. What is the specified and typical force required to actuate a key on a QL keyboard? Newtons or ounces please! Dave ql.spodmail.com
Re: [ql-users] QL DVD disk
On Wed, 6 Mar 2002, Phoebus Dokos wrote: IIRC the problem with video output is different from the Audio one (ie there's no disconnection of the drive) meaning you just don 't tell the drive to start and just leave it alone after that. On any QDOS based system esp. due to slave blocking as has been proven time and again, the playback would be erratic (very much so). MPEG2 software based playback takes a severe toll on even fast PCs so unless you have an MPEG2 decoder as you said I don't think it can be done (But with the ARM-QL it will and with GoldFire too due to the DSP capability) Ok, I'm talking Intel here, so you'll have to take the relative performance capabilities of different architectures into account, but... For software DVD playback, with a single-tasking OS, you need 200MHz+, and decode times may exceed the time available if the image is particularly complex, or has a lot of movement. For a multitasking OS, add 50MHz at least. It won't likely be coming to a QL near you anytime soon. Dave
[ql-users] I got one...
Hi all, Thanks to Phoebus, I am now in possession of a US QL. It's S13-003595, and it has all it's little rubber feet, and every plastic cover. I am guessing from the sticker on the back that it may never have even been opened. The keys show no wear or shininess. Now I just have to wait for the PSU! I also received four microdrive cartridges (you would not believe the reaction of my American co-workers. They usually say Oh they are so cool. When did they come out? and when I say 1983, in England they're usually nonplussed. I also got a SQB with 512K expanderam. I've examined them carefully and am quite certain these are ones I personally assembled back in '87 or thereabouts. So, the chase is joined... Dave ql.spodmail.com
Re: [ql-users] Hove Workshop
On Tue, 5 Mar 2002, Dilwyn Jones wrote: Oh, speaking of when do I get, anyone heard from Jonathan Dent recently regarding soql TCP/IP and its progress (or lack of)? I would just like to add that as soon as I have an EtherIDE prototype in my hands, I will be sending it to him Dave qlspodmailcom
Re: [ql-users] SuperQ Board, US QL
On Sun, 3 Mar 2002, ZN wrote: I think these correct the 8301 ULA timing to US specs (60Hz), but I can't be sure, I've only had a glance at a US QL If the US QLs have an interrupt to write out the video memory 60 times a second, doesn't that mean they must run a good deal slower than their 50Hz counterparts? Dave
Re: [ql-users] QL Stuff needed
On Sat, 2 Mar 2002 [EMAIL PROTECTED] wrote: I have a Trump Card for you - 15.00 pounds. Call me if you want it because there is a show ion Sunday and I may sell it otherwise. If this is still available, I'll have it. Pleas etell me where/how to make payment if some lucky bugger hasn't snapped it up ;) Dave ql.spodmail.com
Re: [ql-users] Sir Clive was really right :-)
On Fri, 1 Mar 2002, Phoebus Dokos wrote: http://wwwkeytroniccom/home/keyboards/keyboardshtml (etc) What connection? The membranes internally (There is a page in there discussing the advantage of membranes over microswitches ;-)) Or you could follow the thinclients link (copied below) and see an OBVIOUS similarity of concept http://wwwkeytroniccom/home/keyboards/thinclient/thinclienthtml PS: I'm looking for a broken keyboard membrane The main panel needs to be complete and not folded or distorted, as I need to be able to measure it accurately It will be used for measurement for a potential membrane replacement Thanks :o) Dave qlspodmailcom
Re: [ql-users] Sir Clive was really right :-)
On Fri, 1 Mar 2002, Phoebus Dokos wrote: impatient youth (can't you wait until Saturday?):-) No, this has to be a broken one, because I need to destroy it to measure it The internal measurements are vital Dave qlspodmailcom
Re: [ql-users] Sir Clive was really right :-)
On Fri, 1 Mar 2002, Phoebus Dokos wrote: What other stuff you have you might want to part with? There is a For Sale/Wanted section in the board I put up at qlspodmailcom If you list your items for sale there, you may get a higher offer than you think I'm looking for a variety of items, so I may be the main buyer ;) Dave qlspodmailcom
Re: [ql-users] Sir Clive was really right :-)
On Fri, 1 Mar 2002, ZN wrote: Why? A contact resistance of anything up to snip It's the physical characteristics I need to measure, not the layout The bubbles are about 13mm in diameter and the spacing is, IIRC 027mm those neurons are about to be reused so don't hold me accountable if I'm wrong Several of the bubbles in a single row are connected together by virtue of narrow cutouts on the spacer - 5 or 6, usually This reduces pressure buildup in the bubble, when it's pressed into Samsung membranes were separable, had no connections between the 'bubbles', were made of clear material, and had thick silver lines you could even solder to with some attention, and the contact points had small graphite circles printed on them Very erly sinclair membranes were very similar to the Samsung ones, just not separable and without the graphite pads The largest majority of Sinclar membranes were glued together (with a glue that chemically interacted with the signal lines), were made of milky white material that resembles drafting transparency, had very thin silver-on-thallium plating that would easily corrode (soldering is completely out of the question here), and would eventually go brittle with heat and crack Essentially the same as with the Spectrum That's better :o) Ok, now all I need is a draft sheet of the exact physical positioning, and the location and dimensions of every slot, cutout, locating notch, etc ;) Thanks for the construction info - it's useful, and will be used Thanks :o) Dave qlspodmailcom
[ql-users] Stella
Hi all, Does anyone have any information about a version of Stella that runs on ARM processors? Apparently, it's an advanced version of SMSQ/E I'd be interested to know if anyone's seen, heard of, smelled or otherwise licensed this code? Dave qlspodmailcom
Re: [ql-users] SuperQ Board
There were two types of mouse interface... One was a 9 pin serial mouse, and the other was a DIN socket that also used a serial mouse, but I don't have the pinout. I recall most were the 9 pin connectors. I don't recommend using one in an In Car Entertainment Ssstem ;) Dave On Wed, 27 Feb 2002, Phoebus R. Dokos wrote: Anybody knows what kind of mouse a Sandy Super Q-Board takes? (Also do you know if it works with ICE?) Phoebus
Re: [ql-users] SuperQ Board
On Wed, 27 Feb 2002, Phoebus Dokos wrote: That has the 9 pin... so it takes a standard PC one or is it a little different? They were standard PC serial mice. Hehe aren't we the joker here ;-) It's not only you that were a fan of ICE! Anyway I just bought a Sandy SuperQ-Board plus 4 US QLs, 60 cartridges (including my long lost ICE utilities cart. - I do have the ROM) , a US ZX81 WITH Printer (TS 1000) :-) Want one? A QL would be nice. :o) I'm mid-arrangements for a floppy i/f and odds and ends on loan, and that would round things off nicely. That would make a good basis for a development system. Does the US QL have any hardware differences, or just OS differences and a different modulator? Dave ql.spodmail.com
Re: [ql-users] SuperQ Board
On Wed, 27 Feb 2002, Tony Firshman wrote: Quite a lot of noise suppression components etc to meet FCC requirements. I don't know of anything else. Hmmm. So if that zinc paint was around back then, they could have just painted the inside of the case with it ;) The inside of the ARM-QL case would be painted with it, if it wasn't all metal anyway. ;) Dave ql.spodmail.com
Re: [ql-users] Frank Davis - accident
On Sun, 24 Feb 2002, Tony Firshman wrote: I guess they both owe their lives to seat belts (and air bags?) I drive a minivan - a Dodge Grand Caravan. These minivans seat 7 with ease, 9 at a pinch. I bought mine after being t-boned by an SUV while driving an Olds - in the US, about half the vehicles on the road are SUVs, trucks or minivans. I bought it because it was high up, so most of the action would be below head height, and because it puts distance between you and the accident - front and rear. I don't know what kind of minivan they had, but it probably had something to do with it. Dave
Re: [ql-users] Frank Davis - accident
On Sun, 24 Feb 2002, Phoebus R. Dokos wrote: I beg to differ Dave, It is now proven that SUVs trucks and minivans are a lot more dangerous to their passengers than regular cars... (Institute of highway safety says it not me ;-) So I am very happy with my Toyota Yaris (Echo they call it in the US) and its 42 mpg ;-) My chosen subject: accident investigation. That is a serious mis-statement of the statistics used by governments world-wide to disuade people from driving larger vehicles. Usually, the person killed is the driver of the lighter vehicle. SUVs and minivans are involved in accidents where there is a higher risk of a fatality, but that risk is biased towards the driver of the lighter vehicle. You're far more likely to survive in a minivan. Two vehicles hit each other head on. One weighs 1000 lbs and one weighs 2000 lbs. Assuming no energy absorption by the chassis... The total velocity is 60mph, and the total weight is 3000 lbs. The 2000 lb vehicle will slow from 30 mph to 10 mph. The 1000 lb vehicle will slow from 30 mph to -10 mph. The relative acceleration for the 1000 lb vehicle is twice that of the 2000 lb vehicle. (Granted, this ignores differences in restraint systems, energy absorption systems and etc) I studied accident investigation - I wanted to be an air accident investigator. Dave
Re: [ql-users] Sprite movement and relative info.
On Fri, 15 Feb 2002, Bill Waugh wrote: Nope that was a graphics prog, remember the fancy lenslock do dah ??? Oh how I hated those... Dave ql.spodmail.com
Re: [ql-users] Sprite movement and relative info.
On Fri, 15 Feb 2002, Tony Firshman wrote: .. but with supercharge, I could work out most by eye. Yes, but what does that say about the shape of your lenses? ;) Dave ql.spodmail.com
[ql-users] Well I never!
Hi all, I got an email back from Lau today. It would seem he IS the Lau I knew back in '85! :o) We're just starting the whole catching up on old times thing... Thanks for hooking me up, guys! Dave
Re: [ql-users] Well I never!
On Tue, 12 Feb 2002, Malcolm Cadman wrote: The small world of email :-) Ok, so were is Arnie Gardner? :o) Dave ql.spodmail.com
Re: [ql-users] Re: Q-less
On Sat, 9 Feb 2002, Tony Firshman wrote: I'm building a powered backplane which will take power from a switched mode PSU. Such things as 50/60Hz and voltages won't be an issue. ... and that is what Mplane and Qplane have done from day one of course. Like I said, this is a one-off with a couple of differences - it's a butterfly design, to keep the traces *really* short, and it'll have test points on an extra connector. By one off, I mean there will be only one. Not for sale. No more emails please. If you want a backplane, Tony has some very nice ones at good prices. Dave ql.spodmail.com
Re: [ql-users] elf compilers
On Sat, 9 Feb 2002, Tony Firshman wrote: I remember a long session with Freddy and Lau in an Eindhoven room Lau? Lau? I knew a Lau, though I never met him. If Lau reads this list, Lau, does the name Dave Park rind any bells with you? *grins* Dave ql.spodmail.com
Re: [ql-users] elf compilers
On Sat, 9 Feb 2002, Phoebus R. Dokos wrote: Lau = Laurence Reeves, author of Minerva :-) The name is *very* familiar. I remember talking with someone who IIRC lived in London, around 84-85, who was called Lau, and I lost track of them when I lost all my worldly goods in a house fire (I lost track of many school friends, all my contacts, and most of my possessions in one go) Could someone who knows him ask if he knows e, so we'll know if it is the same Lau? If it is, I'd really like to get in touch w/ him... Dave ql.spodmail.com
RE: [ql-users] ms-users-and-smalltalk-list
On Thu, 7 Feb 2002, Norman Dunbar wrote: [ND] I think your hardware posts are pretty tedious - [RZ] but they are on-topic Yes, I agree, and didn't say that they weren't. However, there is a ql-developers list for hardware ? So, effectively, all the hardware stuff in ql-users *is* OT in that respect - no-one has complained about that. Well, hardware *development* has an appropriate group, but general hardware discussion belongs here as much as anywhere... Can a listmom please write a charter for the list, which automatically gets mailed out to all new signups, and defines what's on or off topic, how large .sigs can be, etc? :o) Also, if anyone feels any specialist lists should be set up (ql-advocacy, ql-pubchat, ql-fetist anyone? ;) I run a listserver. Dave ql.spodmail.com
RE: [ql-users] ms-users-and-smalltalk-list
On Thu, 7 Feb 2002, Norman Dunbar wrote: Also, if anyone feels any specialist lists should be set up (ql-advocacy, ql-pubchat, ql-fetist anyone? ;) I run a listserver. ql_fetist - interesting. What's one of them ? :o) Argh, typo! ql-fetish... The way some people go on about the QL it's *definitely* sexual... They say things like it's long, hard, black, and about 6 deep or insert OS here is the best... ;) Dave ql.spodmail.com Web-based chat coming soon - much better than the current board...
RE: [ql-users] ms-users-and-smalltalk-list
On Thu, 7 Feb 2002 [EMAIL PROTECTED] wrote: Web-based chat coming soon - much better than the current board... But then I wouldn't be able to read the messages as they arrive throughout the day like I can with email. Our web access is monitored. That would be: better than the board currently at ql.spodmail.com, not better than this list. Can you telnet or SSH? Dave ql.spodmail.com
RE: [ql-users] ms-users-and-smalltalk-list
On Thu, 7 Feb 2002 [EMAIL PROTECTED] wrote: Can't telnet. SSH? Please excuse my ignorance of that particular TLA :O) SSH is the Secure SHell. It's essentially telnet by SSL... All traffic is encrypted both ways. Whenever you're telnetting to a Linux machine, SSH does the same job securely. Dave ql.spodmail.com
Re: [ql-users] [OT] Disclaimer, was ms-users-and-smalltalk-list
On Thu, 7 Feb 2002, Norman Dunbar wrote: This email is intended only for the use of the addressees named above and may be confidential or legally privileged. If you are not an addressee you must not read it and must not use any information contained in it, nor copy it, nor inform any person other than Lynx Financial Systems or the addressees of its existence or contents. If you have received this email and are not a named addressee, please delete it and notify the Lynx Financial Systems IT Department on 0113 2892990. If the email arrives in your mailbox, and is addressed to your email address, then you are the addressee. If you face any criminal or civil liability as a result of your use/misuse of the information contained within, you could reasonably sue the company for negligence (they did mail it to you in error in the first place). Luckily, such disclaimers are legal nonsense - they're unenforceable, as has been proven in the UK and US in many cases. It's in the same category as clickwrap licenses... On the subject of virii and off-topicness, I would just like to say that it is *variety* that makes lists interesting, and as long as the discussion does eventually return to the subject matter at hand, that's ok. Dave ql.spodmail.com
Re: [ql-users] Re: Q-less
On Thu, 7 Feb 2002, Phoebus R. Dokos wrote: Why don't you ask Nasta for a Q-Plane? or Tony for a M-Plane (not good to re-invent the wheel) I'm not making this for general sale. This is a one-off backplane with a good quality SMPS and test points, that will allow me to do testing and qualification of assembled boards - think of it as an EtherIDE test jig... Wayy ahead of you there contact me if you are interested :-) I'm interested... Email me :o) Thanks for all the hardware offers folks - I have a shopping list and a modest budget, and will be emailing you guys shortly :o) Dave ql.spodmail.com
Re: [ql-users] ms-users-and-smalltalk-list
On Tue, 5 Feb 2002, Tony Firshman wrote: If the virus has come via the list, then I think it _is_ on topic, and the information is interesting. Not only that, it serves as a reminder of why QLs are so great. No viruses! BTW: I'm still QL-less... Scary huh? Dave ql.spodmail.com
Re: [ql-users] Surplus QL ED drives
On Mon, 4 Feb 2002, ZN wrote: Well, yes, there's just one problem: they are from IBM and have NO jumpers. It still may be possible to get them to work on a GC/SGC, I'm looking into it. I believe most IBM floppies have a 0 ohm link on the board, which if removed decides the 0/1 drive ID... I remember modifying a batch of IBM ED drives a few years ago for use with Acorns... This may not be true with all drives, however... Dave ql.spodmail.com
Re: [ql-users] Surplus QL ED drives
On Mon, 4 Feb 2002, Dilwyn Jones wrote: Do they have any disks too - the drives are no good while the disks are in short supply. They do work with DD and SD disks too... Dave ql.spodmail.com
Re: [ql-users] Virus
On Mon, 4 Feb 2002, Dave wrote: ...and since the machine is moistly idle while defragging... Did I really typo that? Egads! *blush* Dave ql.spodmail.com
Re: [ql-users] Surplus QL ED drives
On Mon, 4 Feb 2002, Dilwyn Jones wrote: As long as you don't try to read the DD and HD disks on DD or HD drives afterwards (almost always give bad or changed medium errors). Someone did explain to me why this happens some time ago, but can't remember (different track width, or stronger/weaker recording signal?) The gap is much narrower, which results in a much smaller magnetised patch on the surface of the platter. When a DD head tries to read it, because the feature is narrower than the width of the gap, it shows up as a double spike... Anyway, these drives are so cheap, you could buy extras and send the floppy actually shoved in a drive, like expensive wrapping paper ;) Dave ql.spodmail.com
[ql-users] EtherIDE update...
Hi all, Well, the EtherIDE board is coming along slowly. Devices have been selected and layouts discussed. This will be a very busy little board, with overlaps and a few engineering challenges. The provisional spec is quite impressive, but we may have to drop one of two design options that conflict because of the amount of space they take up. Remember, this board will mimic, and be software/driver compatible to the Goldfire board, as far as that is possible to do with a machine that's still being developed. Sorry I've been a little quiet lately, I've been concentrating on matters closer to home. Now those matters are behind me, I will be devoting more time and energy to this project with Nasta. If anyone has any questions or ideas, they can email me privately. Also, ql.spodmail.com is coming along slowly. I'm still working on the interactive SBasic manual, which will have cross-version comparisons. The main thing hampering me is lack of information/manuals... Take care all... Dave ql.spodmail.com
Re: [ql-users] Sound sampler...
On Fri, 18 Jan 2002, Malcolm Lear wrote: Hi Dave I know that William James worked on a sound sampler board, but I'm not sure if it plugged in the ROM socket. I'll contact him and find out. Thanks, appreciated :o) Dave ql.spodmail.com
Re: [ql-users] CF Readers part IX (The Post Office strikes back!)
On Fri, 18 Jan 2002, Phoebus R. Dokos wrote: For all of you that ordered one or more CF readers, I would appreciate it if you contact me the moment you receive them so I can cross you off the list :-) (Just to feel okay about myself :-) What about the people who ordered none or less? Dave
[ql-users] Sound sampler...
I recall that a couple of years ago someone was working on a sound sampler. I think it could sample sound, and play it back. Basically an A/D and D/A converter. I think it plugged into the ROM socket. Does anyone have any information about this? Dave ql.spodmail.com
[ql-users] Q60, Goldfire and everything...
Hi again... I've received a couple of emails from people, and it's made me a bit worried. People are asking me if they should hold off the purchase of an upgrade, or Q60, based on something that may be released in the future. Not I, not anybody, knows when things will be released. When they are, the next best thing will be right around the corner. If you're thinking of buying a Q40 or Q60, go buy one! Don't hold off for 6 or 12 months for some mystery product. Don't hold out for a new IDE interface if you can get a 2nd hand one from a dealer. We don't know when, or even if, any project will happen, until the boxed card is sat on a dealer's shelf. Don't gamble on that uncertainty. Go buy your upgrades. That was a public service announcement from me. Dave ql.spodmail.com
Re: [ql-users] Another floating idea...
On Wed, 16 Jan 2002, Malcolm Cadman wrote: If the hardware developers can successfully co-operate then it will benefit all of us, as users have different needs, as well as different amounts that they can afford to spend. I am communicating with both the Q60 and goldfire developers. Obviously, both of them want their platform supported first, and I'm aiming for where the market is, which is right between them ;) Here are the key points: The EtherQL will be 100% compatible (bar base address) with the ethernet which is (and already was) planned for Goldfire. That part of Goldfire has already progressed well along the development path. The important thing is to leverage the drivers and software that would be developed, to make them available to QL-based and QX0-based machines too. Obviously the first release will fit the QL-base, because that's what the majority of developers (and customers) have. Shortly afterwards, a software/driver identical version will be released for the Q60. The main difference will be the Q60 will support full 10/100 operation, whereas on a base QL, 100 mbit operation will have to be disabled. If we plan right, the port will also be able to emulate an ultra-fast traditional net port. The drivers and software issue is more complicated. I'm reaching out now to those people who have knowledge in the area. I would like to see simple SuperBASIC socket-handling commands and C libraries supporting it at launch, and at least one functional program for web, mail and telnet that works with the card. These people will have cards long before the general release. If anyone else out there is willing and capable to help in one of these projects, I will happily support you and provide you with any information you need. If you write software you think you could charge 5 quid for, I'll happily publish it for you. If you are happy to do it for free, I'll provide the download site, and bundle it with the card. Registered developers :) will of course get the most up-to-date and detailed specs, and first access to the hardware when it is ready. Either way, I look forward to working with you all... Dave ql.spodmail.com
[ql-users] Another floating idea...
Once again, no promises. I'm just floating this idea to monitor the comments and criticisms, to help me shape the future shape of my projects. I'm going to outline an imaginary product. A full size QL expansion card with the following specification: 2 IDE channels, supporting 4 IDE devices. Standard headers. 1 IDE device supporting a CompactFlash adapter (on board) and a 2.5, 2.5GB standard 5200RPM IDE HD, on board. 1 optional 10/100 ethernet interface. The board would have two configurations: Standard, which would have the IDE circuitry, and compact flash adaptor. It could, in this configuration, come as standard with a 2.5GB drive, on board. The drive could be omitted if required. EtherIDE, which would be as above, plus 10/100 ethernet. The interface would automatically configure as a 10mbit interface if connected to a QL, and 10/100 if connected to a processor fast enough to handle 10/100 (680X0 25MHz+, say) Although it would be possible to provide the board with ethernet and no IDE, this makes no economic sense, so for those just wanting ethernet, a smaller board would be provided. Comments? Criticisms? Dave ql.spodmail.com
Re: [ql-users] Another floating idea...
On Wed, 16 Jan 2002, Phoebus R. Dokos wrote: So I hear... ;-) How come everyone's heard about this except me and Nasta? ;P Well at least a sound generating chip even with FM synthesis...As for samples I am not talking about 16bit stereo 44 KHz sound.. best I could hope was mono 8 bit 22 KHz... (I think that could be feasible)... If you're willing to spend $50 or $60 on a sound card, and can find 50 others who would, I'll do it. I just happen to have 50 AY-3-8910's here ;) Seriously, tho... The GF has all that. For the 50 or 60 you might spend on a half-decent sound card... Invest the money in a high-interest savings account, and then when the GF arrives, you'll have all the money you need ;) That's why I said IF possible :-) And that's also why YOU HAVE TO finish the GF! May you be infested with the cracks of a thousand keyboard membranes ;P Dave ql.spodmail.com
Re: Re: [ql-users] Compact Flash Adapters.
From: Wolfgang Lenerz [EMAIL PROTECTED] Date: Mon 14/Jan/2002 16:16 GMT To: [EMAIL PROTECTED] Subject: Re: Re: [ql-users] Compact Flash Adapters. On 13 Jan 2002, at 20:50, Dave Walker wrote: As far as I know none of those could take the adapter and be able to access it directly from within the QL side of the system? I would have thought that it would work under QPC if windows can see it as a normal drive, thanks to the WONDERFUL DOS device! Wolfgang, The issue I was refering to is not whether it would work at all - but whether I could upgrade DiscOVER to handle it. To do so one needs Direct Sector Access - ideally to the whole drive including the partition table, although if one could even get raw wsector access to every sector within a particular DOS partition this would probably be enough. As far as I know this is not supported by any version of QPC - only access to the QXL.WIN type of file within a DOS media. The DOS2 device in QPC2 gives one access at the file level (which I use a lot) and not the raw sector level - or if so I have missed how one gets it! Dave ___ Never pay another Internet phone bill! Freeserve AnyTime, for all the Internet access you want, day and night, only £12.99 per month. Sign-up at http://www.freeserve.com/time/anytime
Re: Re: [ql-users] Compact Flash Adapters.
From: Phoebus R. Dokos [EMAIL PROTECTED] Date: Sun 13/Jan/2002 18:40 GMT To: [EMAIL PROTECTED] Subject: Re: [ql-users] Compact Flash Adapters. At 06:25 ìì 13/1/2002 +, you wrote: For cards smaller than 32 Megs yes it will... Cameras usually format the cards as FAT-12 drives and SMSQ supports that. If it's larger than that, Dave Walker's MultiDiscOVER probably will... (You have to check with Dave for that). DiscOVER (all variants) can already handle FAT12 and FAT16. I was thinking of adding FAT32 support as well if anyone wanted it, but as FAT16 gets you up to 2Gb on a parition it did not seem particularily urgent. Possibly more useful would be upgrade the filename handling on MSDOS format media to recognise long file names rather than just the 8.3 format. The change that might be needed to get DiscOVER to work with these devices is a (small) one around the original opening code if any special device name is needed to open it in direct sector access mode. Having said that it may be sufficient to simply set the type as WIN and the format as IBM - I would have to check if that combination would get DiscOVER into the code that tries to identify a hard disk partition type. If not it is a minor change to allow it. Dave ___ Never pay another Internet phone bill! Freeserve AnyTime, for all the Internet access you want, day and night, only £12.99 per month. Sign-up at http://www.freeserve.com/time/anytime
Re: Re: [ql-users] Compact Flash Adapters.
From: Phoebus R. Dokos [EMAIL PROTECTED] Date: Sun 13/Jan/2002 19:37 GMT To: [EMAIL PROTECTED] Subject: Re: Re: [ql-users] Compact Flash Adapters. snip also I had a question... I don't remember right off hand if c68 supports special 060 commands and the ... I am asking this because I m in the process of discussing the possibility of a in-car GF or Q60 based MP3 player with the CF... If is supported then we could port an MP3 program to it... else we'll have to use Linux... (:-() . The best thing about that application is that Slave blocking or limitations of the IO system won't matter since in essence the system would be monotasking :-) In principle c68 recognises the idea of processors up to the 040 (not specifically the 060), and also the Coldfire processor. However although there is support there it has probably never been thoroughly tested so it may need further work to guarantee that only legal isntructions are generated. Also, I do not know if GWASS supports the full instruction set of the higher processors (although knowing George Gwilt it probably dos!). Dave ___ Never pay another Internet phone bill! Freeserve AnyTime, for all the Internet access you want, day and night, only £12.99 per month. Sign-up at http://www.freeserve.com/time/anytime
Re: [ql-users] Happy New Year (and with a BITTER lesson to be lea rned) Love Live QLs
- Original Message - From: Malcolm Cadman [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, January 03, 2002 10:47 PM Subject: Re: [ql-users] Happy New Year (and with a BITTER lesson to be lea rned) Love Live QLs My laptop is is dual boot (with the OS in separate partitions so they do not interfer with each other). The performance under Win2K is noticeably faster than under Win95. I do have 256Mb of memory on the machine and I think Win2K makes better use of extra memory than Win9x. Trust you to have the luxurious hardware, Dave :-) It is work that gives me a decent spec laptop (and it is not that speedy at only 600MHz). My home machine is sigificantly better and has a larger monitor attached which is great for running QPC2. When are you going to attend a London Quanta Group meeting, we would love to see you with your speedy laptop ? I have now put the London Quanta dates in my diary (since Novemeber) and it is just a case of whether when the day arrives another conflicting appointment is on it. I play a lot of bridge - and in the last few months these have co-incided with London Quanta meetings. Dave
Re: Re: [ql-users] Happy New Year (and with a BITTER lesson to be lea rned) Love Live QLs
From: Thierry Godefroy [EMAIL PROTECTED] Date: Thu 03/Jan/2002 16:06 GMT To: ql-users [EMAIL PROTECTED] Subject: Re: [ql-users] Happy New Year (and with a BITTER lesson to be lea rned) Love Live QLs On Thu, 3 Jan 2002 15:27:56 - , Norman Dunbar wrote: Well, I'm running QPC2v2 on Win2k - what's wrong with it ? Apart from being slowest than Win95, My experience is that as long as you ahve at least 128Mb of memory then Win2K outperformas any of the Win9x variants. more bloated (if at all possible) and giving you no way to run in TRUE DOS (a MUST on desktop PCs for QXL !), nothing is wrong... This point I have to give you! Or is it (sorry, the Win2k stuff) only for Laptops ? We have a couple of Compaq Evos which run Win2k very nicely. It may run nicely, this is not to say that it makes a good usage of the machine ressources: re-install Win95 and compare the speeds of the same software under both OSes: you will be _amazed_ by the speed difference... My laptop is is dual boot (with the OS in separate partitions so they do not interfer with each other). The performance under Win2K is noticeably faster than under Win95. I do have 256Mb of memory on the machine and I think Win2K makes better use of extra memory than Win9x. Dave Walker ___ Never pay another Internet phone bill! Freeserve AnyTime, for all the Internet access you want, day and night, only £12.99 per month. Sign-up at http://www.freeserve.com/time/anytime
Re: [ql-users] QPC
Ian, You don't by any chance have something loaded like anti-virus software that tries to control all access to the floppy do you? If so, it may be disabling the sector level type of access that is needed by QPC. You certainly do not want to disable the 32-bit mode drivers as this will stop any access to FAT32 partitions. Dave - Original Message - From: Ian Pizer [EMAIL PROTECTED] To: ql-users [EMAIL PROTECTED] Sent: Tuesday, September 25, 2001 8:26 PM Subject: [ql-users] QPC Hi Marcel I have found how to get QPC to read FLP1_, but then it refuses to find DOS1,2,3,4 Here is how: In Control Panel,System,Performance,File System,Troubleshooting: Set Disable all 32 bit Protected-mode disk drivers. Then restart Windows. (Windows also loses D,E and F) I suppose this means something to you. Cheers, Ian Pizer, 49 ch. Machery, 1292 Chambesy, Geneva, Switzerland. e-mail [EMAIL PROTECTED] tel.41227581410 AKA [EMAIL PROTECTED]
Re: [ql-users] CDRom driver
There should be no problem with burning raw images. Certainly software such as Nero or WinCD has this as an option. Dave - Original Message - From: Wolfgang Lenerz [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, September 03, 2001 6:26 PM Subject: Re: [ql-users] CDRom driver Thanks to Peter Claus for their fast answer. So it has to be a raw image. I presume there is no way to burn that under Windows, unless anybody knows better? Wolfgang - www.wlenerz.com
Re: [ql-users] Counte Coup
You can always run in full screen mode! The other thing is if you are using QPC2 v2 and you start it in a window then you can actually drag the edges of the window after QPC2 has started. This will keep the same QL screen resolution that QPC2 was launched with but increase the screen area used scaling everything proportionally. It can distort the fonts, but I have found in most cases this is not a problem. Dave - Original Message - From: Mills [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Sunday, August 12, 2001 7:25 PM Subject: [ql-users] Counte Coup QLEA (at Bramerton, near Norwich) was a successful QL user group, until a PC user joined them and converted them over to using PCs. One of our (ACCUS) members still goes and is hoping persuade them that you can use a QL as well as a Wintel computer. When the other members of Bramerton see QPC they complain that the QL screen (the 3 boxes) takes up only a small part of the screen. Is there any way of increasing the proportion of the screen used? When the 512x256 mode on QPC is selected the QL screen is to big for the PC screen. Our member is using a notebook running at 800x600 resolution. ACCUS (Anglia Classic Computer Users Society) http://www.planet14.sonow.com/comp/accus/ Down with the large computer monopolies.
Re: [ql-users] Another MIllenium style bug
Tony, We will be well placed to implement this for C programs at least!My brother and I are already upgrading c68 to support 64 bit integers so we are thinking ahead :). Of course whether by then we still be able to see a screen or type on a keyboard is another question! Dave - Original Message - From: Tony Firshman [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, July 05, 2001 11:41 PM Subject: [ql-users] Another MIllenium style bug Is the QL GCC going to be hit in 2038 or so by the 32bit limit in the std C time function. Are there any plans for a 64bit time function? Well this is positive forward planning. I will only be 94 then, and Dave Walker will be younger (8-)# -- 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: Q40/Q60 device drivers (was: Re: [ql-users] Derek Stewart BB)
Interesting - I also have a similar source (possibly differently commented?).. At one time I had a CST SCSI interface and I actually managed to modify the code to accept different hard drives. However one observation is that the source include the Tony Tebby floppy and ram disk drivers and a rudimentary Toolkit set of extensions - so is he happy if we publish those sources (albeit it is a very old version). Dave - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, July 02, 2001 6:56 PM Subject: Re: Q40/Q60 device drivers (was: Re: [ql-users] Derek Stewart BB) On Mon, 2 Jul 2001, Malcolm Lear wrote: I have the documented sources for the CST SCSI hard drive if anyone requires them. Hi, is it possible to publish these sources? What about the rights of the author, do you know anything about this? If they're well documented, we might learn a lot. Claus __ powered by Q60 * Motorola 68060 / 80 MHz * 80 MB RAM * 30 GB Hard Disk
Re: [ql-users] NEXT in FOR-loop
The result for negative numbers is quite understandable if one assumes that the number is always rounded down by the INT operation.In languages such as C whether one rounds towards 0 or rounds downwards is often an implementation defined feature - i.e. there is no official standard. Dave - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, June 19, 2001 10:05 AM Subject: RE: [ql-users] NEXT in FOR-loop Morning all, I managed to do a bit of experimenting on the INT(x) problem last night. Counting down gave the following results: 3.03 3 3.02 3 3.01 3 The correct result for 3 this time is because the 3 3 internal value printed as 3 will be slightly higher 2.99 2 and rounded down. 2.98 2 2.97 2 2.96 2 2.95 2 The results for negative numbers are strange and I can't attribute this to rounding. I wonder if the original QL would have given the same results using it's software floating point routines instead of the 68040's FPU. -2.95 -3 -3.03 -4 -2.96 -3 -3.02 -4 -2.97 -3 -3.01 -4 -2.98 -3 -3 -3 -2.99 -3 -2.99 -3 -3 -3 -2.98 -3 -3.01 -4 -2.97 -3 -3.02 -4 -2.96 -3 -3.03 -4 -2.95 -3 I was hoping to try an equivalent test in C and Assembler using the 68040 FINT and FINTRZ instructions but didn't have time. Ian. -Original Message- From: zeljko.nastasic Sent: 18 June 2001 16:43 To: ql-users Cc: zeljko.nastasic Subject: RE: [ql-users] NEXT in FOR-loop On 6/18/01 at 3:44 PM Claude Mourier 00 wrote: Thank's a lot for all the answers. But this is quite annoying : especially because behavior is not the same for PRINT and INT. Better if PRINT returns something like 2.9 (in fact SMS loves exponential form I personaly hate). I'm not sure but I think even FDEC$(n, 9, 8) returns 3.0. Claude No, it's Print. Eventually, you have to print it and that's where the rounding happens. FDEC$ does an implicit print, so again you cannot escape rounding. The only way would be to get the actual float representation from memory as 6 bytes and convert them 'manually'. Nastan Visit our website at http://www.ubswarburg.com This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. This message is provided for informational purposes and should not be construed as a solicitation or offer to buy or sell any securities or related financial instruments.
Re: [ql-users] Metacomco C and Sandy CP/M
Norman, If you cannot find it I also have a copy. However I never use it! Dave - Original Message - From: Norman Dunbar [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, May 10, 2001 8:11 AM Subject: RE: [ql-users] Metacomco C and Sandy CP/M I think, somewhere in my 'vast' collections of 'useful' stuff, that I have a disc given to me by Geraint Jones a long time ago (well, three house moves ago) which has a copy of the Metacomco C compiler but adapted so that it doesn't need the ROM plugged in. If I ever find it, I'll let you know. I can't remember if I ever tried it out, but as far as I remember, MCC was seriously bugged anyway - and as we now have the much better and still being developed C68 ... Norman. PS. I'm now the 'proud' user of Windows 2000 Professional here at work. My old NT box had too many problems just recently due to a faulty disc, so I had a rebuild and upgraded to Win2K in the process. I'll have to get QPC2v2 installed again and see how it hangs together. -- -- Norman Dunbar EMail: [EMAIL PROTECTED] Database/Unix administrator Phone: 0113 289 6265 Lynx Financial Systems Ltd. Fax: 0113 201 7265 URL: http://www.LynxFinancialSystems.com -- --
Re: [ql-users] Calling Photon from Hyper Browse
Tarquin Mills wrote: I have not found a way to call photon and pass it arguments e.g. execute_w win1_photon;"win_neon2.jpg\d2" as execute_w (Turbo toolkit) and exec (Toolkit II) only take contants as arguments, i.e. 10 path$="win1_" 20 img$="neon2.jpg" 30 execute path$'photon;"'path$img$'\d2"' does not work. I do not have a copy of the Soql yet, does it support PPP yet, and where do you get it from as sourceforge only seem to have the source. Turbo's EXECUTE appears to have its own way of launching jobs. I guess it is only meant for Trubo jobs; it stuffs 6 extra bytes on the job stack (in front of everything else). This will confuse most jobs which expect to find the OS documented WORD for number of channel ID's (followed by ID's) and WORD for length of option string and string. Solution: don't use Turbo's esoteric EXECUTE command. To use Toolkit 2's EX command (or EXEC/EW/EXEC_W): EX win1_photon;"win1_neon2.jpg\d2" The reason why EX path$'photon;"'path$img$'\d2"' will not work is because EX can only see that you have passed one parameter; a single string parameter (the semicolon separator is lost within the first '' and becomes a string character rather than parameter delimiter). BTW the dithering defaults to a level suitable for the mode so the \d2 (default mode 4 8) is not probably necessary. Regards, Dave.
Re: [ql-users] coulours on SMSQ
Per Witte wrote:
Dave Westbury writes:
...different data structures in Qlib'd programs, perhaps it wasn't.
Probably not. Arrays are treated identically to the parser in Qlib :)
I think the problem was that the functions first scanned the name table for
specific integer array names (and checked they were of the correct size) before
filling them from the data stream. When QLib'd they always responded not-found
so I guessed the nametable wasn't used within compiled programs?.
I cant say Ive hit too many limitations using Qlib with SMSQ/E.
I found that many that it was too daunting to consider rewriting it (just did a
quick try and got 388 MISTakes). It was a very specific program anyway (a Yamaha
SY35 synthesiser voice filer/editor) which required access to MIDI port on a QL.
...un-initialised variables,
The one thing I dislike most about SMSQ is the practice of setting unused
variables to zero or empty string. I have spent hours looking for bugs that
turned out to be a typo in a variable name! Something like the INSTR_CASE
command for changing the default behaviour would be welcome.
try
a$='abc': PRINT ('x'a$)(4)
chr$(0), strange.
If the location and format of Turbo arrays were known, and the parser could
be told to shut up about array parameters passed to m/c procedures, then
extention toolkits could test for Turbo and take the appropriate action.
Unless the header or storage format are very different, even patching some
non supported toolkits might be possible. Just a thought.
The new TURBO_V will apparently allow some powerful array structures
manipulations.
Regards,
Dave.
Re: [ql-users] Hyper Browse
Dilwyn Jones wrote: I have tried using both releases of HyperBrowser and have been unable to prevent it issuing the error reported at line 390. Are any extra software or extensions needed to get it working? What am I doing wrong? Try changing filename extension delimiter from underscore to dot? (IIRC that was the problem; filename fixed in binary of compiled). Regards, Dave.
Re: [ql-users] QL Graphical Browser
Phoebus wrote: Whoever does a QL browser please note. Just wondering *That's for Dave Westbury*... would it be possible to make an extension out of your Photon program that could be used elsewhere too? It can be used from SuperBASIC (or compiled) or used as a Thing. You can launch (emit?) as many photons as you like, so hopefully this should make it easier for Web browsing over TCP/IP. On the topic of a QL web browser, with so many going over to QPC2 ;-( , isn't it only going to be Q40/60, GF and maybe SGC+SuperHermes users that would have any real interest? I could understand the interest in a mail program using Jon's TCP/IP on QPC2 but the thought of someone running a windows application/emulator to run a QL web browser seems a bit perverse (...um, yes I think that is the word I would use ;-) Regards, Dave.
Re: [ql-users] Sbasic
Wolfgang Lenerz wrote: Can anyone repeat this? Doesn't crash here. Marcel Sorry Marcel, just tried the QPC2 demo and it does, viz: (1) Launch QPC2 demo (2) type program into basic 10 DEF PROC a(b,c%) 20 END DEF a (3) QSAVE ram1_p (4) EXEP 'SBASIC' (5) switch to daughter SBASIC (6) type QLRUN ram1_p QED Regards, Dave.
Re: [ql-users] coulours on SMSQ
Tony Firshman wrote: QA.RESRI. I haven't tried QDOS/Minerva on this yet, I hope they do the same. Ask Laurence Reeves ([EMAIL PROTECTED]) In the usual tradition of asking first before RTFM I found Minerva manual page ASM.6 details how BV.CHxxx is dealt with. If enough memory can not be reserved then address held at BV_SSSAV is called. Per wrote: Superbasic returns straight back to the parser on an OM error in sb.resri. This concurs. SMSQ I did a little trace of QA.RESRI but (due to stack manipulations which screwed up tracing) it went awry. But I do recall seeing BV_SSSAV referenced before I got an address error exception call (so I assumed it was incorrect reference). Marcel, does this mean D0 will not return ERR_IMEM but simply stop SBASIC with error? Which basically (sic) is the required result anyway. eg just call BV.CHRIX/QA.RESRI and if it returns all is well. Per wrote: I also notice that the value pointers in the name table have all gone absolute, ie even SB variable values are stored in some user heap outside the SB. Havent got round to arrays yet, but all my array-handling toolkits still seem to work, so perhaps no change there? Now that rings a bell. In early coding days I wrote some array handling SBASIC commands (which, given a channel, filled arrays directly from a MIDI data dump). They worked well under SMSQ but failed when I qliberated the program. I just put it down to different data structures in Qlib'd programs, perhaps it wasn't. Qlib'ing the final program was doomed to fail anyway since by then I had extensively used SMSQ SBASIC features/constructs that Qlib rejected :-( O/T Qliberator I wonder what the status of Qlib sources are, wasn't it going to be updated to deal with SMSQ some time ago? Although SBASIC is as quick as compiled, you can't circulate EasyPtr extensions separately to your programs. Writing a new program using TPTR and Turbo would be OK but I wouldn't like to completely rewrite my old EasyPtr programs to use it :-( Regards, Dave.
Re: [ql-users] Pointer read
...But QPTR is only a BASIC toolkit to access the IOP WM calls. This only would have made QPTR able to use events under SMSQ v2.71+ No, QPTR is just the basic interface to the PE, so it can't do more than the PE itself... Sorry if I'm being pedantic, but I said QPTR (the file) is the BASIC toolkit: I assume that the update to it was simply to change the RPTR BASIC Proc to now include (rather than ignore) the event bits (ie, as a terminating parameter to, and a return parameter from, the BASIC parameter list). The underlying PTR_GEN trap IOP.RPTR would need to support the previously unused term bits (which must have been ignored by Qptr until the update - as is/are bits 23 to 8 which are used by WMAN only (see QPTR manual Update page 2))). Regards, Dave.
Re: [ql-users] merlin tonto ql clone
To add to what Dilwyn has said, the OPD/Tonto shared many components with the QL at the hardware level, but was very different at the operating system level. The software Dilwyn mentioned (OPD/QL Interchange is mentioned on my web site, but not available for download as I have never looked at removing the original copy protection. One thing that OPD had was a variant of Exchange, so you can exchange Quill/Archive/Abacus/Easel files with the OPD using my software. If you have a real need for it, then let me know and I could put together and email you an unprotected version. Dave - Original Message - From: "Dilwyn Jones" [EMAIL PROTECTED] To: "QL Users List" [EMAIL PROTECTED] Sent: Tuesday, February 27, 2001 6:35 PM Subject: Re: [ql-users] merlin tonto ql clone Does anyone know something about the merlin tonto personel computer ? It is said its a ql clone but i cannot find much about it. Is it fully compatible with the standard ql? A company called ICL developed a machine called the OPD (One Per Desk) based on QL hardware, and this appeared in several variants, one was the Tonto. The hardware is based on a QL, but it is not fully compatible with a QL. I think it uses the same microdrive cartridges as the QLbut in a different format, so a QL cannot read Tonto/OPD cartridges and a Tonto cannot read QL software cartridges. Dave Walker developed software many years ago to allow exchange of software between OPD cartridges and QL cartridges. The software ran on a QL and was called OPD Interchange. I don't know if the software is still available. Dave Walker's website is on www.itimpi.freeserve.co.uk By the way, this mailing list prefers plain text emails. -- Dilwyn Jones [EMAIL PROTECTED] http://www.soft.net.uk/dj/index.html
Re: [ql-users] C68/QPC2/qdir_read
Christopher, You are correct in that the C68 qdir_read function does not work on the QPC2 DOS device. The cause is a slight difference in behaviour of the ioa.open trap#2 call when the open mode=4 (to specify a directory mode open) for the DOS device compared to other devices. For most devices if you open give the open call a string such as "WIN1_LIB_FRED" then if the WIN1_LIB_ directory exists it will be opened, and if not the WIN1_ directory will be opened.On the DOS device you have to give the exact directory name with no trailing information or it fails (e.g. "DOS_LIB_" - and this would fail if the LIB_ sub-directory did not exist). The qdir_read function is written this way so that it behaves correctly whether you have "soft" or "hard" directories on your system. It would be possible to rewrite the logic of the qdir_read function to take account of the existence of "hard" directories and thus work correctly on the DOS device - but this would make the code slightly larger. It all depends on whether Marcel can make the open behaviour of the DOS device be the same as other devices (Marcel what do you think?). Dave - Original Message - From: "Christopher Cave" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Monday, February 12, 2001 5:44 PM Subject: [ql-users] C68/QPC2/qdir_read Has anyone else come across a problem with the C68 function qdir_read when it is applied to DOS directories under QPC2? Calls to open, read and close files all work O.K. but not qdir_read. Christopher Cave
