[ql-users] QPac2 Colourways vs System Pallete
Has anyone else tried to set up the system palette to mimic the old black/green colourway? I have created what seems like a sensible theme using QCoCo but when I load it, Files V1.26 (QPac2 V1.42) exhibits the following behaviour: 1) The empty device name loose items in the Source/Destination Directory window are solid black rather than a white/green stipple 2) The View window ink is black (on black paper!) 3) The Sort by window unselected loose items (including ESC) are white-on-black instead of black-on-white 4) The Sort by window unavailable loose items are green-on-black instead of green-on-white Also, at the risk of upsetting Phoebus and Marcel, does anyone know how I can replace the colourful new system sprites with the boring old ones? :-) In case it's relevant, I'm using QPCII V3.23 (SMSQ/E V3.08) in High-colour mode... John ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
Re: [ql-users] QPac2 Colourways vs System Pallete
John Hall wrote: Has anyone else tried to set up the system palette to mimic the old black/green colourway? Oops! Before someone sets off on a wild goose chase, I've now checked my old QPCII set-up and reminded myself that what I'm actually trying to achieve is the equivalent of the following QPac2 configuration: Main border colourway: white/green Menu window colourway: black/green However, my comments re. the Files thing in my previous message still apply... John ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
Re: [ql-users] QPac2 Colourways vs System Pallete
John Hall wrote: Has anyone else tried to set up the system palette to mimic the old black/green colourway? No need as all these palettes are already inbuilt! There are 4 system palettes in the system and all are pre-set to the 4 old colourways. And of course you can configure Qpac2 to use any of the 4 palettes, just like before. 1) The empty device name loose items in the Source/Destination Directory window are solid black rather than a white/green stipple That's the Shaded area colour. 2) The View window ink is black (on black paper!) Probably application window colours. Also, at the risk of upsetting Phoebus and Marcel, does anyone know how I can replace the colourful new system sprites with the boring old ones? :-) You could add the smsq_gold_sysspr module to the SMSQ/E file, it should override the other one, or use the code therein to create a LRESPR extension. I think just the header has to be cut away for this to work. Or, simplest solution actually, just don't start in high colour mode ;-) Marcel ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
[ql-users] Fw: c/ o Geoff Wicks / QL
- Original Message - From: rankus at us dot es To: Sent: Wednesday, December 29, 2004 9:28 AM Subject: c/ o Geoff Wicks / QL I received the below email privately. Is there anyone who is interested in replying to Manuel? I have removed the pictures as they made the mailing over the limits for this list, Best wishes, Geoff Hi. I have the following material: * Sinclair QL (1986) and the original packaging. It runs pretty well. Has no problems. Membrane is OK. * 12 mdvs cartriges formated two weeks ago. * The four original PSION programs (in 4 mdvs): EASEL,QUILL,ABACUS and ARCHIVE. * Monitor (12 monocrome, green), with original packaging. * Sinclair QL user and programmer manuals * Two covers each for 4 mdvs * Technical drawings (circuitry, repairs,ecc) ¿ Could you advise me about the prices ?. I would appreciate very much your information. Looking forward to hearing from you. Bye, Manuel. Find Attached few photos. ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
Re: [ql-users] QDT Demo
On Fri, 31 Dec 2004 11:09:51 -0500, Phoebus Dokos [EMAIL PROTECTED] wrote: So assuming we are already up in 1024 x 512 and we issue a WMON 50,50 (as per M.K. usual standard which I have adopted as itleaves sufficient space for the button frame - thanks Marcel) and then issue either a DISP_SIZE 512,256 (which should switch to512x256 Hi-colour) or DISP_COLOUR 0,512 (Which should switch to Mode 4 512 x 256) the OS dies - And when I mean dies... diescompletely -Only a hardware reset will bring it back. However if you keep your job 0 within the confines of the 512x256 (upper half corner of the screen) then switching is no problem. You will kill a couple of PE jobs here and there but that's to be expected. Is this not the same problem as I highlighted on this very some time ago - the problem is that the SuperBasic windows exceed the visible screen area and so smsq/e tried to kill the job (it kills all jobs which would have any part of their windows outside the reduced screen area). I can see why this happens (although it should NOT affect job 0 - which should surely force #0,#1 and #2 into the standard WMON setup (in 512x256) - possibly just stop the current job from running and close any windows which would fall outside 512x256. Without background screen writing, it is impossible to let other jobs run. However, my suggestion was that jobs should not be killed when the screen resolution is altered - only when they are brought to the top of the pile (so that they would be able to write to the windows which are outside of the screen area). In this way, if the user switched from 1024x512 to 512x256 to run a small program, they could carry on using the high resolution program, provided that they changed the screen mode back before PICKing the job. Another option could be for the task scheduler to increase the screen size if a task cannot fit within the confines of the current screen - though I do not think that this would look very neat. Any other suggestions on the best way of handling these ?? I thought someone had offered to look at background screen drawing - did they ever do anything other than offer their services?? -- Rich Mellor RWAP Services 26 Oak Road, Shelfield, Walsall, West Midlands WS4 1RQ http://www.rwapservices.co.uk/ ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
Re: [ql-users] QDT Demo
In message [EMAIL PROTECTED], Rich Mellor [EMAIL PROTECTED] writes On Thu, 30 Dec 2004 13:39:08 -0800, James Hunkins [EMAIL PROTECTED] wrote: Hi Malcolm, clip For the installation, you should run the basic program that came with the install. It should run everything for you, including the unzipping and starting the official installer. The intent is that the three files are self contained. Just by running the basic program, you don't need to know much else. This is one of the problems with the QL being over 20 years old before it has software with automated installers. The first thing people do is try to copy the software across to their desired device themselves and configure it - not thinking that they should read the instructions and actually try to LRUN the boot file on the disk. I actually did try it from the Demo floppy as it has LRUN flp1_QDINST_BAS printed on it. Although it didn't seem to want to start from there. Thus I made a directory on the win drive called 'QDT' and copied the files from the floppy to there. The problem was that my 'unzip' was running the version that I have on the win drive, which is 5.32. This threw up some errors in the 'ICONS' of QDT. Using the 'unzip' provided solved that, and software installed with no difficulty. I note, too, from your other email that 'unzip' is now at version v.5.40. I believe that all of these things are important and worth commenting on. As those of us who have some expertise should make it as easy as possible for users to install software ... especially when it is something which is highly complex. If I wore a hat I would take it off to you for the QWord installation process, which is the neatest I have come across. -- Malcolm Cadman ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
Re: [ql-users] QDT Demo
In message [EMAIL PROTECTED], James Hunkins [EMAIL PROTECTED] writes Hi Malcolm, Could you forward me separately to the email address below copies of: - install_log file (should be either in your win1_QDTINST_ folder or more likely in your win1_QDT_ folder (assuming that is where you installed it)? - qdt.log (should be in your win1_QDT_ folder, same assumption) - your boot file(s) Also, any additional notes about your install process would be appreciated. For the installation, you should run the basic program that came with the install. It should run everything for you, including the unzipping and starting the official installer. The intent is that the three files are self contained. Just by running the basic program, you don't need to know much else. You might want to go to the QDT website to download the PDF QDT Installer User Manual. It has complete screen shots and lots more detail. It also has a few more user manuals plus errata, FAQs, etc. http://www.jdh-stech.comThere is a link near the top of this page that takes you directly to QDT contact at jdh-stech dot comFor email of any issues or need for support If anyone else has any problems with this install, please contact me directly as quickly as possible as I am racing to get the final full production release ready. By the way, the EXIT button only happens at the end of the install itself. The bottom right button is always the next step button, whether it be NEXT, START, or EXIT. I am really curious why you do not have anything visible on your screen to start with, especially since you are running it on QPC. Perhaps it has to do with the way you started things versus using the automated install from the basic program. Malcolm, one last thing, where did you get the more recent InfoZip copy? Thanks, Jim. I don't think it is anything to do with your software. After looking at it again today the problem for me is that my version of the 'Wman' is v1.53, which has been superceded for the High Color screens. As your software is quite rightly exploiting the latest graphic abilities, this is where I have been caught out. It took me some time to realise it ! . as I wasn't looking for that as the cause, and there were no error messages being shown. Your Installer is well implemented. I am just saying make it as foolproof as possible ... especially as it can be quite a lengthy process. Maybe put in some 'dummy values' into the boxes that are blank - for example 'Empty'. With regard to the InfoZip copy I obtained it through one of the London QL Quanta group members. Presumably it was downloaded off the web. -- Malcolm Cadman ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
Re: [ql-users] QDT Demo
In message [EMAIL PROTECTED], Phoebus Dokos [EMAIL PROTECTED] writes SNIP If you do not use PE applications at all (speaking of my experience) the system is just fine. Problems start once you use some PE applications which don't fare too well with either extensions or the memory scheme (I would assume as I haven't been able to point my finger on it yet) I replied to some of this in the other mail but what do you mean about 'extensions' which extensions do you refer to. Maybe it is the amount of hard drives/their size that I have (I have currently 3 exceeding a combined 160 Gigs capacity) that causes the OS to go nuts (or at least some applications). I seem to recall that the Q40 had limit to the size of the partitions available for SMSQ but that may have been fixed. As David McCann pointed out the limit was 256mb but I suspect this has now been addressed. Nonetheless you are, of course, running this on an ISA slot controller which possibly has firmware which is not designed to handle large drives. Doubt this would fragment memory though. The last version of SMSQ/E which was 'approved' for the Q40 / Q60 by its builders was, I believe, patched to remove problems with the caches. Again, I am out of the loop with this now and the Q40 is rarely switched on so I am not sure but I ran it all day today on v 3.07 and saw no fragmentation on my sysmon. SNIP My other piece of redundant hardware is my MinisQL since that is really pretty slow in comparison to the other stuff but I thought I would drag it out and install QDT on it as a test. It installed perfectly and adapted itself to the smaller screen with no problems (thought you would like to know that Jim). Well I wouldn't call my Aurora setup redundant (or slow) for that matter myself but that's strictly a personal opinion. (However if it is redundant I'll be glad to relieve you of it ;-) -for free of course- :-P ) Would this be to go with the Aurora and SGC that you asked me to hold onto for you which you then did not reply to my email about asking if you wanted it? It is only redundant in the sense of not being used in everyday situations. Marcel found it very useful in the development of the colour Aurora Drivers and I find it useful for odd tasks like disk copying and testing software (and SMSQ/E) Mind you, if anyone wants a full MinisQL I can oblige. The Aurora SMSQ/e (current version 3.03 with colour drivers) actually has no problems and the colour drivers are to say the least excellent! And to me at least they are quite fast :-) And for you infidels out there proof of that is only 1 purchase away ;-) (buy QWord for the Aurora and you will see that it is quite fast). BTW: Auroras with Minerva MKII installed as per Simon's (Goodwin) confirmation CAN play Digital Audio at 10KHz mono (which is quite good actually)... so all Aurora users out there better start buying stuff from TF Services (Tony may I remind you that you will need to add a couple of zeroes to that cheque ;-) hehehe) OF course once you have the colour drivers installed to play QWord you cannot use the Minerva can you? BTW the Aurora Colour driver is just a module grafted onto exactly the same core of SMSQ/E as is used in all the other versions (so Marcel recently informed me when we were discussing how to detect the different versions for the SGC - Hi and Lo Colour.). So, if the O/S is at fault so it should fragment on all systems. -- Roy Wood Q Branch. 20 Locks Hill, Portslade, Sussex.BN41 2LB Tel: +44 (0) 1273 386030fax: +44 (0) 1273 430501 web : www.qbranch.demon.co.uk ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
Re: [ql-users] QDT Demo
On Fri, 31 Dec 2004 17:43:42 +, Malcolm Cadman [EMAIL PROTECTED] wrote: cut I don't think it is anything to do with your software. After looking at it again today the problem for me is that my version of the 'Wman' is v1.53, which has been superceded for the High Color screens. Hang on Malcolm - what system are you running this on...?? Smsq/e has wman and ptr_gen incorporated - you should not be loading them separately. QDT only runs under smsq/e if I am correct - therefore you should not be worrying about the version of wman as much as the version of smsq/e As your software is quite rightly exploiting the latest graphic abilities, this is where I have been caught out. It took me some time to realise it ! . as I wasn't looking for that as the cause, and there were no error messages being shown. Your Installer is well implemented. I am just saying make it as foolproof as possible ... especially as it can be quite a lengthy process. I am sure he would appreciate comments on how to make it more foolproof - I am waiting to see this program with baited breath now... -- Rich Mellor RWAP Services 26 Oak Road, Shelfield, Walsall, West Midlands WS4 1RQ http://www.rwapservices.co.uk/ ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
Re: [ql-users] QDT Demo
Fri, 31 Dec 2004 19:26:57 +,() Roy wood [EMAIL PROTECTED] /wrote: In message [EMAIL PROTECTED], Phoebus Dokos [EMAIL PROTECTED] writes SNIP If you do not use PE applications at all (speaking of my experience) the system is just fine. Problems start once you use some PE applications which don't fare too well with either extensions or the memory scheme (I would assume as I haven't been able to point my finger on it yet) I replied to some of this in the other mail but what do you mean about 'extensions' which extensions do you refer to. Yes but I just finished running an exhaustive memory test and no memory errors were found. So memory problems are out of the question. Regardless of that I removed ALL extensions that I am running and only left QMenu and QPAC2. Sysmon continues reporting fragmentation snip I seem to recall that the Q40 had limit to the size of the partitions available for SMSQ but that may have been fixed. As David McCann pointed out the limit was 256mb but I suspect this has now been addressed. Yes Nonetheless you are, of course, running this on an ISA slot controller which possibly has firmware which is not designed to handle large drives. Doubt this would fragment memory though. That is silly. You cannot use PC (x86 code) firmware on a Q40! Nonetheless all but one of my ISA controllers are dual channel ones and are supported by SMSQ/e as well as QDOS Classic and Q40 Linux. Many people use them (among others Fabrizio which bought it on his own) The last version of SMSQ/E which was 'approved' for the Q40 / Q60 by its builders was, I believe, patched to remove problems with the caches. Again, I am out of the loop with this now and the Q40 is rarely switched on so I am not sure but I ran it all day today on v 3.07 and saw no fragmentation on my sysmon. Maybe my Sysmon or QPAC2 version is what's causing the problems. I don't know if it has changed since last year. SNIP My other piece of redundant hardware is my MinisQL since that is really pretty slow in comparison to the other stuff but I thought I would drag it out and install QDT on it as a test. It installed perfectly and adapted itself to the smaller screen with no problems (thought you would like to know that Jim). Well I wouldn't call my Aurora setup redundant (or slow) for that matter myself but that's strictly a personal opinion. (However if it is redundant I'll be glad to relieve you of it ;-) -for free of course- :-P ) Would this be to go with the Aurora and SGC that you asked me to hold onto for you which you then did not reply to my email about asking if you wanted it? But I did reply to your email! Twice actually! However the above reference was a joke (unless you want indeed to give it for free :-P It is only redundant in the sense of not being used in everyday situations. Marcel found it very useful in the development of the colour Aurora Drivers and I find it useful for odd tasks like disk copying and testing software (and SMSQ/E) Mind you, if anyone wants a full MinisQL I can oblige. OF course once you have the colour drivers installed to play QWord you cannot use the Minerva can you? Once you have SMSQ/e you cannot use Minerva (except for the I2C part) but that doesn't stop you from NOT loading SMSQ/e (where QWord plays quite nicely and floppy speed is faster than with SMSQ/e) BTW the Aurora Colour driver is just a module grafted onto exactly the same core of SMSQ/E as is used in all the other versions (so Marcel recently informed me when we were discussing how to detect the different versions for the SGC - Hi and Lo Colour.). So, if the O/S is at fault so it should fragment on all systems. Not exactly. Not all SMSQ/e's are the same and AFAIK they don't all have EXACTLY the same code. What would happen then if you tried to use Cache modes commands on QPC or Gold Card? Phoebus ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
Re: [ql-users] QDT Demo
In message [EMAIL PROTECTED], Phoebus Dokos [EMAIL PROTECTED] writes SNIP Yes but I just finished running an exhaustive memory test and no memory errors were found. So memory problems are out of the question. No I meant the problem was with the way the memory was used on the system not with the system itself. Regardless of that I removed ALL extensions that I am running and only left QMenu and QPAC2. Sysmon continues reporting fragmentation As Rich Mellor so rightly asks, What version of Sysmon is it. This has been updated. That is silly. You cannot use PC (x86 code) firmware on a Q40! Wrong. The firmware is what is on the chip that does the controlling. That firmware is, these days, often flash memory so it can be updated to support new media (as happens often in CD Writers etc.) The hardware and O/S has to interface with the onboard firmware in order to control the device. I thought you went to college to learn this stuff!! (He he) Nonetheless all but one of my ISA controllers are dual channel ones and are supported by SMSQ/e as well as QDOS Classic and Q40 Linux. Many people use them (among others Fabrizio which bought it on his own) Probably not the likely cause of the memory problem as I said. SNIP Well I wouldn't call my Aurora setup redundant (or slow) for that matter myself but that's strictly a personal opinion. (However if it is redundant I'll be glad to relieve you of it ;-) -for free of course- :-P ) Would this be to go with the Aurora and SGC that you asked me to hold onto for you which you then did not reply to my email about asking if you wanted it? But I did reply to your email! Twice actually! However the above reference was a joke (unless you want indeed to give it for free :-P So was mine but the only reply I got from you was to say you were going to reply. Once you have SMSQ/e you cannot use Minerva (except for the I2C part) but that doesn't stop you from NOT loading SMSQ/e (where QWord plays quite nicely and floppy speed is faster than with SMSQ/e) See my reply to Rich Mellor Not exactly. Not all SMSQ/e's are the same and AFAIK they don't all have EXACTLY the same code. What would happen then if you tried to use Cache modes commands on QPC or Gold Card? They do have different modules added in to support the various hardware differences but the core code is, I have been informed, always the same. I do not think anyone has changed the Cache modes which were written by TT at Peter's behest. -- Roy Wood Q Branch. 20 Locks Hill, Portslade, Sussex.BN41 2LB Tel: +44 (0) 1273 386030fax: +44 (0) 1273 430501 web : www.qbranch.demon.co.uk ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
Re: [ql-users] QDT Demo
In message [EMAIL PROTECTED], Rich Mellor [EMAIL PROTECTED] writes The problem is not helped by the fact that Peter Graf has turned his back on current versions of smsq/e. As the hardware designer, he is best placed to comment and spot where the problems lie. One of the problems I had with him was that, when I reported problems he told me they weren't problems and did nothing about them. Alas, there is no prospect of getting him to work under the smsq/e licence, therefore the smsq/e developers have to struggle on alone. Well that should be no problem since Wolfgang has and uses a Q60 That said - if people do not report problems so that they can be collated together, how is anyone supposed to fix the problems?? 100% agree with that. cut The Aurora SMSQ/e (current version 3.03 with colour drivers) actually has no problems and the colour drivers are to say the least excellent! And to me at least they are quite fast :-) And for you infidels out there proof of that is only 1 purchase away ;-) (buy QWord for the Aurora and you will see that it is quite fast). BTW: Auroras with Minerva MKII installed as per Simon's (Goodwin) confirmation CAN play Digital Audio at 10KHz mono (which is quite good actually)... so all Aurora users out there better start buying stuff from TF Services (Tony may I remind you that you will need to add a couple of zeroes to that cheque ;-) hehehe) OF course once you have the colour drivers installed to play QWord you cannot use the Minerva can you? Yes, but Roy, you can play QWord under Minerva - you do not need smsq/e at all :-) That is why we are so proud of it. I can see your pride but Phoebus was just extolling the virtues of SMSQ/E colour Aurora drivers. In any case, surely the Minerva MKII extensions would still work from within smsq/e - or do they actually use some of the Minerva operating system? I don't think they work although some bits were adapted to run under SMSQ/E. The thing is that SMSQ/E replaces whatever is underneath and Minerva is just and operating system on a ROM so as far as SMSQ/E is concerned it is not there. BTW the Aurora Colour driver is just a module grafted onto exactly the same core of SMSQ/E as is used in all the other versions (so Marcel recently informed me when we were discussing how to detect the different versions for the SGC - Hi and Lo Colour.). So, if the O/S is at fault so it should fragment on all systems. I agree... However, I think the problem is with some of the actual software in use on the Q40 - from what I recall, there were various patches released including ones for Qliberated programs ?? Sysmon may need updating to cope - Phoebus is at fault here - making a sweeping statement that smsq/e is not reliable on Q40/Q60 is liable to put people off using that operating system, when it actually appears related more to the software he is using. Phoebus, if you don't report details of the actual problems, then please don't make sweeping statements (we get much too many of those on the list). Yes I was going to ask him what version of Sysmon he had - I forgot. I don't recall actual patches for QLiberated programs but the O/S certainly got patched. On my Q40 things would not run which ran perfectly well on a DD systems one. We tested this at the Hove show they came to. I tried all the patches but ProWesS and some QLib programs just would not work correctly. I have already had comments like QWord installer does not work on smsq/w v2.98 but QWord does (this is on the Q40) - without knowing exactly what the user sees on screen (ie. what happens), how am I supposed to know whether it is smsq/e or my installer (I have no Q40/Q60 let alone smsq/e v2.98) I get this sort of thing all the time. One user tied me up for hours asking about creating a QXL.WIN file on his ZIP drive from QPC2 I talked him through it and it kept failing. Of course the one question I had forgotten to ask (didn't think I would need to) was if he had a disk in the drive. He didn't. -- Roy Wood Q Branch. 20 Locks Hill, Portslade, Sussex.BN41 2LB Tel: +44 (0) 1273 386030fax: +44 (0) 1273 430501 web : www.qbranch.demon.co.uk ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
Re: [ql-users] QDT Demo
Fri, 31 Dec 2004 20:46:26 +,() Roy wood [EMAIL PROTECTED] /wrote: In message [EMAIL PROTECTED], Phoebus Dokos [EMAIL PROTECTED] writes SNIP Yes but I just finished running an exhaustive memory test and no memory errors were found. So memory problems are out of the question. No I meant the problem was with the way the memory was used on the system not with the system itself. Regardless of that I removed ALL extensions that I am running and only left QMenu and QPAC2. Sysmon continues reporting fragmentation As Rich Mellor so rightly asks, What version of Sysmon is it. This has been updated. That is silly. You cannot use PC (x86 code) firmware on a Q40! Wrong. The firmware is what is on the chip that does the controlling. That firmware is, these days, often flash memory so it can be updated to support new media (as happens often in CD Writers etc.) The hardware and O/S has to interface with the onboard firmware in order to control the device. I thought you went to college to learn this stuff!! (He he) I am sorry but you are wrong. By Firmware we mean software (specific to a CPU unless someone has created JAVA bytecode firmware that I don't know about) that is put on a hardware add on for ANY number of reasons. There are kinds of firmware of course and some are completely foreign to the platform (good example is the old Turtle beach firmware that was in two parts. One was the PC code that was used as a loader for the 68000 that was on board that had a different firmware altogether (that was being downloaded) and which happened to be 68K code. What is on the CHIP COULD be firmware if the Chip was an SCC (Single Chip Computer... like the superHermes or the 8049) however that is not the case with the controller chips unless they are caching controllers which do not function on the Q40 anyway. What you probably mean is either Logic Code (as in hardware coding such as the Mach chips on the Aurora or Lattice Chips on the Qx0s) or Microcode (which isn't the case here anyway) By and large though firmware is specific to the hardware platform for which the add on is destined to. That is why modern PCI cards for example do not have anything like that but softload it onto the card so that cards can function in different systems (ie Macs and PCs) Nonetheless all but one of my ISA controllers are dual channel ones and are supported by SMSQ/e as well as QDOS Classic and Q40 Linux. Many people use them (among others Fabrizio which bought it on his own) Probably not the likely cause of the memory problem as I said. SNIP Once you have SMSQ/e you cannot use Minerva (except for the I2C part) but that doesn't stop you from NOT loading SMSQ/e (where QWord plays quite nicely and floppy speed is faster than with SMSQ/e) See my reply to Rich Mellor Actually I2C works fine (I have it here and use it as well..) the MKii part works great. They do have different modules added in to support the various hardware differences but the core code is, I have been informed, always the same. I do not think anyone has changed the Cache modes which were written by TT at Peter's behest. I think they were changed right after SMSQ/e's license was changed but I am not sure. -- Using Opera's revolutionary e-mail client: http://www.opera.com/m2/ ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
Re: [ql-users] AVG7
There's no way that AVG dumps anything into Documents and Settings... That's all I need is a flat contradiction ! Thanks so much. Check Grisoft forum for more prob's ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
Re: [ql-users] OT: AVG7
Fri, 31 Dec 2004 23:17:13 -,() John Hall [EMAIL PROTECTED] /wrote: Hi John, David Tubbs wrote: There's no way that AVG dumps anything into Documents and Settings... That's all I need is a flat contradiction ! Thanks so much. Has it occurred to you that the tone of the response might be influenced by the tone of the original message? Actually I didn't try for a special tone :-) However if my tone was kinda harsh I apologise :-) I have installed AVG 7 actually in more than a dozen machines and I haven't had any probs with it. That was the reason for being rather emphatic... AAAnnnyywwway since this IS off topic lets leave it at that :-) Check Grisoft forum for more prob's If the issue has been raised in the (PC software) supplier's forum, why complain here? True too although I also looked at Grisoft's website but I found no forum per se anyway... just a FAQ. From what I've read he probably had a failed installation which could lead in temporary files being left over in his Documents And Settings (but still not under the main directory) Happy New Year and... QL Forever! And to all a good night :-) Ffibys ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
Re: [ql-users] QDT Demo
In message [EMAIL PROTECTED], Rich Mellor [EMAIL PROTECTED] writes On Fri, 31 Dec 2004 17:43:42 +, Malcolm Cadman [EMAIL PROTECTED] wrote: cut I don't think it is anything to do with your software. After looking at it again today the problem for me is that my version of the 'Wman' is v1.53, which has been superceded for the High Color screens. Hang on Malcolm - what system are you running this on...?? Smsq/e has wman and ptr_gen incorporated - you should not be loading them separately. You know that is a thought, Rich. I still use a boot file with QPC2 that I took over from my Gold Card QL system. In that I do implicitly load the QPAC2 files. Today I did try making a boot file just for QDT as a separate item, using the information that Jim's Installer provides - it writes a text file with comments on what additions are required to an existing boot file ( this when you use the Advanced option ( manual ), rather than the automatic version which writes to the existing boot file for you. QDT only runs under smsq/e if I am correct - therefore you should not be worrying about the version of wman as much as the version of smsq/e Umm ... that is why it didn't really occur to me to consider the Wman. How do you check the SMSQ/E version number ? As your software is quite rightly exploiting the latest graphic abilities, this is where I have been caught out. It took me some time to realise it ! . as I wasn't looking for that as the cause, and there were no error messages being shown. Your Installer is well implemented. I am just saying make it as foolproof as possible ... especially as it can be quite a lengthy process. I am sure he would appreciate comments on how to make it more foolproof - I am waiting to see this program with baited breath now... Well, now that I have looked at what the Installer produces, it is a smart piece of work. Which makes it more disappointing that I haven't got a working Demo :-( -- Malcolm Cadman ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
Re: [ql-users] QDT Demo
In message [EMAIL PROTECTED], James Hunkins [EMAIL PROTECTED] writes Thanks for the verification, Malcolm. I have added a couple of notes in the QDT web site FAQs section as to the problems you ran into which should help anyone else who hits them. No problem. That is what Demo's are for. On Dec 31, 2004, at 9:43 AM, Malcolm Cadman wrote: Thanks, Jim. I don't think it is anything to do with your software. After looking at it again today the problem for me is that my version of the 'Wman' is v1.53, which has been superceded for the High Color screens. As your software is quite rightly exploiting the latest graphic abilities, this is where I have been caught out. It took me some time to realise it ! . as I wasn't looking for that as the cause, and there were no error messages being shown. Your Installer is well implemented. I am just saying make it as foolproof as possible ... especially as it can be quite a lengthy process. Maybe put in some 'dummy values' into the boxes that are blank - for example 'Empty'. With regard to the InfoZip copy I obtained it through one of the London QL Quanta group members. Presumably it was downloaded off the web. -- Malcolm Cadman ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
Re: [ql-users] QDT Demo
In message [EMAIL PROTECTED], James Hunkins [EMAIL PROTECTED] writes Maybe Jim's installer does not report Program does not start in the resolution / screen mode . I had debated trying to detect this, but as you probably saw in a recent thread, it isn't all that simple. So instead I went the route trying to make it clear in the system specs and the articles that hi color (256 or more) capabilities are required to run anything to do with QDT. Not a perfect solution but I have enough other things that I need to work out in our systems to make it all happen. QDT and its installer will set the colors properly and automatically as long as the system being used supports 256 or more colors. Thus I made a directory on the win drive called 'QDT' and copied the files from the floppy to there. The problem was that my 'unzip' was running the version that I have on the win drive, which is 5.32. This threw up some errors in the 'ICONS' of QDT. Hmm - what I do not understand is how, if you copied all the files across to win1_QDT_ and ran the installer from there, why did it use YOUR unzip, rather than the one supplied?? Just looked at the basic install program and I don't actually use the location that you type in to start unzip. Instead I do use DATA_USE and PROG_USE and then do a direct EX unzip call. This I believe should work. I do restore the DATA_USE and PROG_USE to the original settings when done. I will do another install and let you know the results. Could just be my ignorance :-) ... yet you need to know that too, as other users can make similar errors. I have now looked at all the reports in a text editor that QDT does when it installs and you have done a very neat job. Using the 'unzip' provided solved that, and software installed with no difficulty. I note, too, from your other email that 'unzip' is now at version v.5.40. I believe that all of these things are important and worth commenting on. As those of us who have some expertise should make it as easy as possible for users to install software ... especially when it is something which is highly complex. Yes, all this is useful information and I do take notes. I won't always make changes (can't implement everything for everyone or else it would never get done) do often do. And I will continue to update the FAQs page on the web to help other users as appropriate. By the way, Phoebus and I have talked about the QWord install and some of the plans for it. For most programs, it will make an excellent installer and I hope that you guys can make it available for everyone to use. The QDT installer, while someone scripted, turned into something a lot more complex than most people would need, due to what it was installing. So I am very glad you guys are doing your separate efforts for a 'universal' install program. I would agree with that. A universal installer would be a nice feature to have. Recent QL software is also getting very sophisticated. I remember that it took me a while to understand how set up QPAC2 and the Pointer Environment to my liking. Yet once achieved there was no going back. More recently I set up Launchpad, and I now find that indispensable ... like how did I ever manage without it :-) -- Malcolm Cadman ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
Re: [ql-users] QDT Demo
In message [EMAIL PROTECTED], Rich Mellor [EMAIL PROTECTED] writes On Fri, 31 Dec 2004 18:11:29 +, Malcolm Cadman [EMAIL PROTECTED] wrote: In message [EMAIL PROTECTED], Rich Mellor [EMAIL PROTECTED] writes On Thu, 30 Dec 2004 13:39:08 -0800, James Hunkins [EMAIL PROTECTED] wrote: Hi Malcolm, clip For the installation, you should run the basic program that came with the install. It should run everything for you, including the unzipping and starting the official installer. The intent is that the three files are self contained. Just by running the basic program, you don't need to know much else. This is one of the problems with the QL being over 20 years old before it has software with automated installers. The first thing people do is try to copy the software across to their desired device themselves and configure it - not thinking that they should read the instructions and actually try to LRUN the boot file on the disk. I actually did try it from the Demo floppy as it has LRUN flp1_QDINST_BAS printed on it. Although it didn't seem to want to start from there. You need to explain more on this please Malcolm - what errors did you see here? Jim cannot fix something that does not want to start from there. Guess you were running it on QPC2 ? Which version and what screen resolution and screen colour mode did you have - please remember that we software developers get told off for actually switching the resolution and colour depth at will. I will need to go through the procedure again to identify those difficulties. Maybe Jim's installer does not report Program does not start in the resolution / screen mode . Yes, that would be a useful report to have. Demo's are all about finding the reactions from real users. Thus I made a directory on the win drive called 'QDT' and copied the files from the floppy to there. The problem was that my 'unzip' was running the version that I have on the win drive, which is 5.32. This threw up some errors in the 'ICONS' of QDT. Hmm - what I do not understand is how, if you copied all the files across to win1_QDT_ and ran the installer from there, why did it use YOUR unzip, rather than the one supplied?? Just my practice to use the unzip version that I have. It has turned out that Jim had used an earlier version. So inadvertently it has highlighted something that we wouldn't have thought of. Using the 'unzip' provided solved that, and software installed with no difficulty. I note, too, from your other email that 'unzip' is now at version v.5.40. I believe that all of these things are important and worth commenting on. As those of us who have some expertise should make it as easy as possible for users to install software ... especially when it is something which is highly complex. If I wore a hat I would take it off to you for the QWord installation process, which is the neatest I have come across. Thankyou Malcolm - we hpoe to make it a little wider ranging so we can adapt it fairly easily to other programs. That is what I figured :-) -- Malcolm Cadman ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
[ql-users] Happy New Year
Happy New Year fellow QLers! I hope you and the QL have a successful 2005. -- Tarquin Mills (Chairman) ACCUS (Anglia Classic Computer Users Society) http://www.speccyverse.me.uk/comp/accus/ ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
Re: [ql-users] Happy New Year
Happy New Year fellow QLers! I hope you and the QL have a successful 2005. Yep, all that :) Hopefully '05 will see me find a place to set my museum out and get my QL stuff exhibited properly so people can play with it. cheers! *raises wineglass* -- adrian/witchy Binary Dinosaurs creator/curator www.binarydinosaurs.co.uk - the UKs biggest home computer collection? ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
[ql-users] QDT Demo
On Dec 31, 2004, at 3:16 PM, Malcolm Cadman wrote: I actually did try it from the Demo floppy as it has LRUN flp1_QDINST_BAS printed on it. Although it didn't seem to want to start from there. Did the basic program not run? If it did run, what did you type in when it asks where the installer programs are? If running from the floppy you would need to enter: flp1_ Demo's are all about finding the reactions from real users. Maybe for some people but this demo had two totally other purposes. 1) to let someone try out the program so that they could understand basically what it is and decide if they want to buy it 2) to let someone test it on their system to make sure that their system can handle it before they purchase it I have been taking user feedback and input on QDT for about four years now, both at shows and then over the last year with my testers. I do expect (and look forward to) additional feedback and reactions of course. Just my practice to use the unzip version that I have. It has turned out that Jim had used an earlier version. So inadvertently it has highlighted something that we wouldn't have thought of. One advantage of using properly tested install setups (all pieces) is that everything has been tested. The supplied install program worked fine with the file. The QL Today guys actually ran it from a floppy to do a final verify before it was shipped. One of the reasons why the unzip was included is that I am aware that there is a difference with different unzip and other archive type software. And when you think about it, the nearest thing to a standard for zip/unzip that I am aware of has been the attempt to match the original PKZIP package. Of course there are different efforts like infozip that Jonathan ported over for us. In other words, pick a 'standard' of the month' :) Cheers, Jim Hunkins JDH Software Technologies ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
Re: [ql-users] QDT Demo
In message [EMAIL PROTECTED], Phoebus Dokos [EMAIL PROTECTED] writes Wrong. The firmware is what is on the chip that does the controlling. That firmware is, these days, often flash memory so it can be updated to support new media (as happens often in CD Writers etc.) The hardware and O/S has to interface with the onboard firmware in order to control the device. I thought you went to college to learn this stuff!! (He he) I am sorry but you are wrong. By Firmware we mean software (specific to a CPU unless someone has created JAVA bytecode firmware that I don't know about) that is put on a hardware add on for ANY number of reasons. There are kinds of firmware of course and some are completely foreign to the platform (good example is the old Turtle beach firmware that was in two parts. One was the PC code that was used as a loader for the 68000 that was on board that had a different firmware altogether (that was being downloaded) and which happened to be 68K code. What are you talking about ? Firmware is what is on the board itself. Each Chip has a set of instructions built into it and you have to interface with the controller to talk to the hardware. How else could you do it. Really this is silly. Every device has to be able to talk to the controlling software. On the SGC there was a standard device to talk to the floppy drives and the 'glue' chip on the SGC talked to that. Both of these were firmware in a s much as they were written to the chip itself . In the case of the ISA controller there is only one kind of firmware and that is the code on teh chips which talks to the hardware. They do have different modules added in to support the various hardware differences but the core code is, I have been informed, always the same. I do not think anyone has changed the Cache modes which were written by TT at Peter's behest. I think they were changed right after SMSQ/e's license was changed but I am not sure. Not as far as I know. -- Roy Wood Q Branch. 20 Locks Hill, Portslade, Sussex.BN41 2LB Tel: +44 (0) 1273 386030fax: +44 (0) 1273 430501 web : www.qbranch.demon.co.uk ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
Re: [ql-users] QDT Demo
Sat, 1 Jan 2005 01:40:00 +,() Roy wood [EMAIL PROTECTED] /wrote: In message [EMAIL PROTECTED], Phoebus Dokos [EMAIL PROTECTED] writes SNIP For the most part minus some problems with older very early Qx0 machines, Qx0s are quite unproblematic and their hardware is quite well documented. So if the hardware is working properly (as it is) why should a hardware designer fix a problem that it is in software? For example it wasn't the hardware's problem that the Q60's couldn't work with SMSQ/e... it was the software that had the MOVEP instructions built in. Wrong again I am afraid. There were many problems with the hardware itself some of which were, I believe, corrected in 'stealth mode'.. Hence the 'Q40 is no longer' supported tag. Tony Firshman identified a number of problems which Peter would not acknowledge and the serial ports were a source of several problems for TT. Software was just a fraction of it. Well I do not think that this is the reason why Q40 is not longer produced. It has firstly been superceded by the Q40i which is a lot better (and this is available as a special order actually IIRC), but because it makes no sense for both to be produced where the speed vs. price difference is negligible. In other words why sell it now when you can buy a Q60 at a very similar price? Yes, but Roy, you can play QWord under Minerva - you do not need smsq/e at all :-) Why bother to use Minerva these days ? Minerva has rather nice features and the best part it works even without any expansion. Moreover it has very good documentation and it is GPLd :-) But lets not get into the same argument again :-) Let's just say I like it and I assume many others (plus it works great with uQLx and Q-emuLator and you can play all Damon Chaplin games on it -to boot ;-) which is invaluable from which everway you look at it :-P In that case get the writing right and don't just lump it all in one sentence. I am sorry but probably my English failed me again :-( I tend to write many times the way I think... and I think in Greek :-) I2C is not a part of Minerva but the Minerva board (the MKII one) to use I2C you need to load the extensions which are nice enough to work as a module under SMSQ/e too. And you need I2C for? Hmm let me see :-) Let my daughter play with Legos, do some crazy DIY stuff that I like, control plant watering systems turn lights on and off when I am gone and read the crazy Pennsylvania temperatures... (some of the things you can do... it's a hobby after all... other people drink!) Hmmm how to you actually see the version of Sysmon? Is it in the configuration options? yep I will look although mine is in German last time I looked... what is the most current version anyway? Ffibys ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
Re: [ql-users] Firmware. Was: QDT Demo
Sat, 1 Jan 2005 01:48:33 +,() Roy wood [EMAIL PROTECTED] /wrote: In message [EMAIL PROTECTED], Phoebus Dokos [EMAIL PROTECTED] writes Wrong. The firmware is what is on the chip that does the controlling. That firmware is, these days, often flash memory so it can be updated to support new media (as happens often in CD Writers etc.) The hardware and O/S has to interface with the onboard firmware in order to control the device. I thought you went to college to learn this stuff!! (He he) And of course here you contradict your own definition. Indeed what I say is just that (ie there is some sort of rom that holds software of some kind for a host cpu), not that the chips themselves (or the Q40 controller which was what started this thread) has software embedded. Single Chip Computer devices (which are of course ICs themselves)do have memory and a CPU and as such potentially they can hold firmware, however just a non-intelligent (ie no CPU) controller IC doesn't. I hope this clears it up the subject Ffibys ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
