Re: [ql-users] New WMAN (was: GD2)
On 14 Nov 2002, at 1:35, Marcel Kilgus wrote: > > WMAN should really be updated to GD2 - any volunteers? > That'd be me again, then... In fact I'm almost done. Since > yesterday all routines accept the new colour word definition, only > a few more lines for the system palette are needed. And some > sensible defaults for that palette (which'll probably be the hardest > task). Three cheers for Marcel! Please be reminded that his work will benefit all platform physically capable of it! > > Yes, there is, I called it ws_scach. And yes, I'm not good at names. You're pretty good at everything else > I hope so. I want to tie up some lose ends like this WMAN thing before > concentrating on the university project. After that I hope others are > sufficiently familiar with the code to start contributing, too (it's > BTW not only SMSQ/E. EasyPtr should be updated as well, for example. > Any volunteers?). Are the sources available? BTW, QPTR pratically doesn't need to be updated - I've done some work on that, and, provided one or two new functions are used, to reduce 24 bit colours to 16 bit and set the correct MS bit, you can use it to produce high colour PE windows from Basic. I'm trying to finish an article for QL Today for that > System palette entries (...) Just a couple of questions here: 1 - Does "button" mean the buttons in the button frame, or also (other) loose items? 2 - I often give my application subwindows different colours to my info subwindows. I'm not sure whether I'm alone in that. If not, we (you!) should, perhaps, provide for it. Wolfgang
[ql-users] SMSQ-E Development
So now that weve argued this license business to exhaustion isnt it time to move on to some practicalities? The license says nothing of HOW were going to work, WHOs going to do WHAT and in WHICH order. So how do we go about this? Quite some work has already been done by various people, such as tidying up the code to make it suitable for general distribution, adding various tools and help utilities, and Marcel has added some significant improvements to the code base which were previously only available to SMSQ-E for QPC. All well and good so far :) We now need to consolidate and take a look at how it is best to proceed. I think this project is going to be very much people-driven rather than goal-driven. The framework we work under will derive from that rather than be the result of a pre-determined, unified plan. I doubt we'll ever be able to agree among ourselves on a common goal, but we may just be able agree on a general direction and some of the obvious sub-goals that arise from that. Communication and some kind of structure therefore become central, or we'll just fumble and then stumble.. One way to build such a framework, one that is both firm, dynamic and distributed, in a practical way, would be to develop a dedicated website for this purpose. It could: Hold general information about the project List the sub-projects List planned developments List the developers and their areas List progress information List the resellers and registrar Allow downloading of components to registered developers Allow downloading of the latest binaries to registered users Hold the documentation Allow downloading of utilities related to development Allow bug reports and feedback Hold a support database (a la M$'s Knowledgebase) ... Im not suggesting the registrar do this as it is a major project in its own right. Of course this may go against the licence as it stands - in practise, though not, if I understand correctly, in spirit. Per
Re: [ql-users] Q40 and Linux
On Wed, 13 Nov 2002 at 17:41:15, Phoebus Dokos wrote: (ref: quantumcentral>) >One thing I didn't figure out yet is how to boot the cd in the first >place (ie where I >can find the boot disks). You could try cd \images \dosutils\rawrite.exe Asks for a disk image: boot.img Asks for drive, enter a: and run again with supp.img on another disk. from a windows box. This is redhat, but I recall others using the same method. You then, of course, boot off the first disk, but I am sure you know that. -- QBBS (QL fido BBS 2:252/67) +44(0)1442-828255 tony@.co.uk http://www.firshman.co.uk Voice: +44(0)1442-828254 Fax: +44(0)1442-828255 TF Services, 29 Longfield Road, TRING, Herts, HP23 4DG
[ql-users] New WMAN (was: GD2)
TonyTebby wrote: > He started getting more into the concept of GD2 !! > > How can anyone do this - has this man a brain the size of a planet? > I can't understand it and I wrote it! I just said I'm getting more into it. Not how much :-) I gather information here and there and it's often enough to do some changes (like the new buffer-less background colour code or the 16bit shadow), but that's it. I wouldn't even dare thinking about other proposals from the list, like background redrawing. > If I remember right, the sprite cache routines check the address of > the sprite (which is likeley to be re-used either if you are editing > the sprite or if you are loading the sprite into the chank of > memory) and the sprite cache version number (pto_vcch in the sprite > header) Argh, I have totally overlooked that you introduced a cache version (so much for my knowledge). Of course, this way it's easy. And it even works! Thanks for the hint. > WMAN should really be updated to GD2 - any volunteers? That'd be me again, then... In fact I'm almost done. Since yesterday all routines accept the new colour word definition, only a few more lines for the system palette are needed. And some sensible defaults for that palette (which'll probably be the hardest task). While I'm at it: last call for comments! I'll attach below the new WMAN specification the way I did implement it. Any suggestions for changes should be done exactly NOW before it gets official! > Until then would someone like to modify the WMAN scroll sprite > generation code to use a new cache version number instead of 0 each > time? There must surely be a byte spare somewhere in the (a2) block > to store the last value used. Yes, there is, I called it ws_scach. And yes, I'm not good at names. > Will this open source software idea ever catch on? I hope so. I want to tie up some lose ends like this WMAN thing before concentrating on the university project. After that I hope others are sufficiently familiar with the code to start contributing, too (it's BTW not only SMSQ/E. EasyPtr should be updated as well, for example. Any volunteers?). Marcel - | | | Vector $7C WM.SETSP | | | | Set system palette entries| | | | Call parameters Return parameters | | | | D1.w start index D1 preserved| | D2.w number of elements D2 preserved| | D3+ all preserved| | | | A0 A0 preserved| | A1 pointer to palette entries / 0 A1 preserved| | A2 A2 preserved| | A3 A3 preserved| | A4 A4 preserved| | A5 not used by any routine | | A6 not used by any routine | | | | Error returns: | | IPARIllegal index number / invalid number of elements | | | Set the entries of the system palette to the values in the buffer, beginning with the index in D1 (counting from 0) and ending with the index D1 + D2 - 1. If A1 = 0 then the entries are taken out of the default table. Otherwise the buffer must hold an array of words with the colour values of the different items. The colour format is the standard WMAN colour format as described elsewhere. | | | Vector $80 WM.GETSP | | | | Read system palette entries | | | | Call parameters Return parameters | | | | D1.w start index / -1D1.w preserved / item count | | D2.w number of elements D2 preserved
Re: [ql-users] Core software and Q60
[EMAIL PROTECTED] wrote: >> Unfortunately this way there's currently no high colour sprite format >> in QXL/QPC (and if anybody's wondering that's one of the reasons why >> the high colour wman is still not finished). > Is this why a mode 32 sprite (as described in the documentaion for GD2) > doesn't work with QPC? Yes, mode 32 sprites were disabled in the mode 32 driver. I think they should work now, though I have only tried mode 64 so far (a golden 3D pointer as standard pointer sprite. Neat). > A mode 4 sprite DOES work (presumably because it is changed to the > appropriate format??). 4 colour, fixed 256 colour and 256 palette colour should always have worked. Marcel
Re: [ql-users] Q40 and Linux
??? 13/11/2002 5:17:02 ??, ?/? Fabrizio Diversi <[EMAIL PROTECTED]> ??: > >Phoebus, >here you can find what you need : >http://linux-q40.sourceforge.net/, iso image of the >Shoestring Linux. >In total it is a full CD (640MB) and a couple of >floppies to boot it only the first time. >Inside the cd you will find all the instruction to >install it. Hi Fabrizio One thing I didn't figure out yet is how to boot the cd in the first place (ie where I can find the boot disks). I can download the CD no problem (it's approx a 10 min. download for me) but there are no instructions on how to re-attach the parts... >Let me know if you need further help, I can send to >you also a copy of my Linux CD if the download of >640MB exceed your bandwidth capacity . Any help will be appreciated. >Anyway pay attention that you need a second HD or you >have to repartition the main HD using MKpart to create >a LNX and Swp partitions, so do not start to fill your >main HD before prepare it for Linux. I left most of my HDD unpartitioned for this reason :-) I got the Q40 to test my SMSQ/E software and re-acquaint myself with Linux. BTW: I want to do pretty much what you did with SMSQ/E (translate it to Greek that is... any pointers you may have would be appreciated :-) I am expecting the sources any day now... Best Regards,
Re: [ql-users] ADSL
Tony , I have the same configuration as you for my personal web pages : - ADSL via a TCP/IP Router with Firewall - Dynamic Ip and DNS provided by www.dyndns.org - Shoestring Linux with Apache Web server but everything run on my Q60 !! Better , don't you ? Ciao Fabrizio --- Tony Firshman <[EMAIL PROTECTED]> wrote: > > Quite an exciting day today. > > ADSL is working and my Linux box now acts as a > gateway for all our > network (Windows and Linux). No more negotiating > for a line. > > As I have a fixed ISP, we have set up Apache as a > web server, so my QL > web page is now on my own machine. > > I will get DNS to host my domain tomorrow hopefully, > but right now it > works as http://81.2.121.145 > > I am looking forward to being able to write scripts, > and do anything I > want (8-)# > -- > QBBS (QL fido BBS 2:252/67) > +44(0)1442-828255 > tony@.co.uk http://www.firshman.co.uk >Voice: +44(0)1442-828254 Fax: > +44(0)1442-828255 > TF Services, 29 Longfield Road, TRING, Herts, > HP23 4DG __ Do you Yahoo!? U2 on LAUNCH - Exclusive greatest hits videos http://launch.yahoo.com/u2
[ql-users] Q40 and Linux
Phoebus, here you can find what you need : http://linux-q40.sourceforge.net/, iso image of the Shoestring Linux. In total it is a full CD (640MB) and a couple of floppies to boot it only the first time. Inside the cd you will find all the instruction to install it. Let me know if you need further help, I can send to you also a copy of my Linux CD if the download of 640MB exceed your bandwidth capacity . Anyway pay attention that you need a second HD or you have to repartition the main HD using MKpart to create a LNX and Swp partitions, so do not start to fill your main HD before prepare it for Linux. Ciao Fabrizio Ciao Fabrizio --- Phoebus Dokos <[EMAIL PROTECTED]> wrote: > > ??? 12/11/2002 6:29:34 ??, ?/? Phoebus Dokos > <[EMAIL PROTECTED]> ??: > > Has anyone installed the latest linux of the Qx0 > linux recently so he could give me > some pointer? > > My Linux skills are very "unpolished" to say the > least and a couple of pointer (ie > which files to download) would be very welcome :-) > > Phoebus > > > __ Do you Yahoo!? U2 on LAUNCH - Exclusive greatest hits videos http://launch.yahoo.com/u2
[ql-users] ADSL
Quite an exciting day today. ADSL is working and my Linux box now acts as a gateway for all our network (Windows and Linux). No more negotiating for a line. As I have a fixed ISP, we have set up Apache as a web server, so my QL web page is now on my own machine. I will get DNS to host my domain tomorrow hopefully, but right now it works as http://81.2.121.145 I am looking forward to being able to write scripts, and do anything I want (8-)# -- QBBS (QL fido BBS 2:252/67) +44(0)1442-828255 tony@.co.uk http://www.firshman.co.uk Voice: +44(0)1442-828254 Fax: +44(0)1442-828255 TF Services, 29 Longfield Road, TRING, Herts, HP23 4DG
[ql-users] Q40 and Linux
??? 12/11/2002 6:29:34 ??, ?/? Phoebus Dokos <[EMAIL PROTECTED]> ??: Has anyone installed the latest linux of the Qx0 linux recently so he could give me some pointer? My Linux skills are very "unpolished" to say the least and a couple of pointer (ie which files to download) would be very welcome :-) Phoebus
Re: [ql-users] Memory
On Wed, 13 Nov 2002 at 18:45:47, Duncan Neithercut wrote: (ref: <[EMAIL PROTECTED]>) >Does anyone know of an extension that allows the RAM seen by SMSQ/E to be >altered. I want to play around with different memory sizes for SMSQ/E on a >Q60. Why not use the Tony Tebby idea of ALCHP eg: 10 new_size = 20:REMark memory size required 20 a=ALCHP(FREE_MEM - new_size) Don't lose the value of a, as one can then do 'RECHP a' to restore without reboot. -- QBBS (QL fido BBS 2:252/67) +44(0)1442-828255 tony@.co.uk http://www.firshman.co.uk Voice: +44(0)1442-828254 Fax: +44(0)1442-828255 TF Services, 29 Longfield Road, TRING, Herts, HP23 4DG
Re: [ql-users] Mouse on the Q40
In message <000f01c28ae6$27552d80$64e17ad5@famwaugh>, Bill Waugh <[EMAIL PROTECTED]> writes try the old type (not PS2) Phoebus, it worked with a three button mouse just fine ( never used the middle button though ). I think it uses sermouse incorporated in SMSQE ( I could be wrong here ) You do not have to load any software it is all built into SMSQ/E which looks at the highest port first and then the next in line until it finds (or not) a mouse. It then loads the software. I have a mouse that works I can send it to you if you want. -- Roy Wood Q Branch, 20 Locks Hill Portslade. Sussex. BN41 2LB. UK Tel : +44 (0)1273 386030 Fax : +44 (0)1273 430501 (New number!) Mobile +44(0)7836 745501 Web : www.qbranch.demon.co.uk
Re: [ql-users] GD2
In a message dated 13/11/02 18:12:27 GMT Standard Time, [EMAIL PROTECTED] writes: All sprites that are drawn on the screen are first converted to native mode and the resulting native mode sprite is stored in a little cache so that you do not need to keep on converting them (this is also the normal way of handling scaleable fonts in Windows, X-Windows etc) Actually, this is a VERY easy way of converting mode 4/8 sprites to, say, mode 33. Just look at the cache after translation and Bob's yout uncle! (If you can find the cache!!.) George
Re: [ql-users] Core software and Q60
In a message dated 13/11/02 11:52:30 GMT Standard Time, [EMAIL PROTECTED] writes: By the way, I remember you having problems with the sprite cache, i.e. that it didn't notice the changes in the sprite edited by sprted. The same problem already exists in WMAN, if you try to define different colours for several scroll/pan bars this will fail as only the first version gets converted. What solution did you come up with? I'd like a clean way to flush the sprite cache but didn't find one so far. Because of this problem, which I mentioned to Jochen who will have passed it to TT, I define all my sprites for use with TurboPTR as mode 4, 8 and 33. This solves the problem, since no translation is needed for the mode 33 sprite, when the mode is, in fact, 33. George
Re: [ql-users] Core software and Q60
In a message dated 12/11/02 17:49:40 GMT Standard Time, [EMAIL PROTECTED] writes: Unfortunately this way there's currently no high colour sprite format in QXL/QPC (and if anybody's wondering that's one of the reasons why the high colour wman is still not finished). Is this why a mode 32 sprite (as described in the documentaion for GD2) doesn't work with QPC? A mode 4 sprite DOES work (presumably because it is changed to the appropriate format??). Any comments? George
Re[2]: [ql-users] Mouse movement / buttons
Hello Marcel, Tuesday, November 12, 2002, 10:56:00 PM, you wrote: MK> Tony Firshman wrote: >>>There used to be ql-developers, but it was turned into a list for Q40 >>>(Linux) specific discussions. >> Indeed? >> I never heard of this one. MK> Well, at least on the Quanta page is written: MK> "This list is for any discussion related to QL Hardware and Q40-Linux MK> be it news, developments, help or queries." MK> Marcel Well spotted Marcel, I only changed the site at the weekend to include this information (www.quanta.org.uk). There has always been a ql-hardware list which started at the same time as ql-users but it has morphed into various discussions due to different needs at certain times throughout its life. -- Best regards, Brucemailto:bruce.nicholls7@;ntlworld.com
Re: [ql-users] Qeymail, last call for suggestions...
In a message dated 12/11/02 14:50:56 GMT Standard Time, [EMAIL PROTECTED] writes: if you are going to use PE and you want to do it 'easily' get hold of EasyPtr (somehow) and there is a totally excellent tutorial avaiulable for download somewhere (Dilwyn's web emporium I think) which shows how to use it without having to go through the same steep learning curve that the author had to. Until I wrote that tutorial (oops !) I used to call the system DifficultPointer - ask Dilwyn, I had many a rant in those days :o) You might also consider looking at TurboPTR which aims also to make life easier for pointer driven programs. If anyone tries this system and finds that additions would make it more useful it is quite on the cards that the system would be upgraded. Have a look at the SQLUG website for the current version (soon to be upgraded in fact!). George
Re: [ql-users] Core software and Q60
In a message dated 12/11/02 17:49:40 GMT Standard Time, [EMAIL PROTECTED] writes: Unfortunately this way there's currently no high colour sprite format in QXL/QPC (and if anybody's wondering that's one of the reasons why the high colour wman is still not finished). Is this why a mode 32 sprite (as described in the documentaion for GD2) doesn't work with QPC? A mode 4 sprite DOES work (presumably because it is changed to the appropriate format??). Any comments? George
[ql-users] Memory
Hi, Does anyone know of an extension that allows the RAM seen by SMSQ/E to be altered. I want to play around with different memory sizes for SMSQ/E on a Q60. Thanks Duncan Neithercut
Re: [ql-users] Core software and Q60
On Thu, 13 Nov 1997, Wolfgang Lenerz wrote: > You're just lucky I don't keep the archives of everything I said... They are available. However, that's not important now. What is important is that I can see you're being very flexible, and I will shut up now :o) Dave
Re: [ql-users] Core software and Q60
On Wed, 13 Nov 2002, Wolfgang Lenerz wrote: > Just to go on record (AGAIN), nothing in this licence stops this > from happening, I've ALWAYS stated that I'd be open to > suggestions in this respect etc. etc. etc... You haven't said this before, but now you have, well, ok, I'll shut up. :o) Dave
Re: [ql-users] GD2 and Hardware
POV does NOT write directly to the screen, it open a scr channel and write there, does not write directly to the screen location !! You do not have to do basically nothing different to have POV working on QPC or on Q60 , I doubt you have an old version. This is my setup : - SETENV "POVINI=win2_pov" in boot file - ex win2_pov_gccpovray;'+i'&nomefile$&' +d0' Thats all, POV use mode 33 or 32 depending on which platform is running. Ciao Fabrizio --- Wolfgang Lenerz <[EMAIL PROTECTED]> wrote: > > 0100,0100,0100On 13 Nov 2002, > at 9:54, Malcolm Lear wrote: > > > 7F00,,> > > > I was wondering if anyone can explain why programs > such as > > > POV Ray only work on Qx0 machines. > > > Mainly because they check whether they ARE > running on such a > machine, and, when not, just give up. > > > The reason: > > > The Qx0 on the one side, and QPC/QXL on the other > side have > incompatible High colour modes. > > > The Qx0 has mode 33, QPC/QXL mode 32. In both cases, > when > you look at the data representing on pixel on the > screen, the colour > is coded on one "word" (16 bits). > > For mode 32, this is coded as: > > > 0100,0100,0100Arial > Narrowgggb rggg > > > Arialwhere for > mode 33 this is coded as: > > 0100,0100,0100grrr > rrbw > > (where W is 1 if any two of the highest bits for > the other colours > are 1) > > > In many applications that doesn't matter, since, > when writing to the > screen they just use the OS (SMSQ/E) which handles > the > "painting" onf th epixels correctly. > > > Other software, however, such a POV, will write to > the screen > directly, this writing a word for each pixel into > the screen memory. > > > To avoid getting funny colours all over the screen, > this software > checks whether it runs on a machine that has the > corresponding > mode - if not, it gives up. > > > Other software is a bit more intelligent > (accomodating?) and paints > the screen corresponding to the mode it runs in... > > > > > > > 7F00,, I can see that > the > > > colours would be incorrect on other platforms such > as QPC, > > > but don't understand why they refuse to run. With > all this > > > talk of maintaining OS compatibility on different > platforms > > > it seems strange that a lot of new software has > major > > > problems dealing with something new like GD2. > > As there are only really 2 major high colour > screen formats, and as > there only thing one really has to do is some byte > shifting, software > could/should be written to take both formats into > account - IF you > really have to write to the screen directly! > > > Wolfgang > > > > __ Do you Yahoo!? U2 on LAUNCH - Exclusive greatest hits videos http://launch.yahoo.com/u2
Re: [ql-users] Core software and Q60
Jerome Grimbert wrote: > } Unfortunately this way there's currently no high colour sprite format > } in QXL/QPC > I beg your pardon, but there is a high colour sprite format for QXL and QPC. > How could sprted run on them otherwise ? Sprted doesn't even offer to edit high colour sprites on QXL/QPC. Only 256 colours. QXL has definitely no 16bit sprites, I think I have re-enabled them on QPC. Not completely sure. Anyway, yesterday evening I had a development spree and the 16bit driver now also accepts mode 64 (32bit true colour) sprites. Only two dozens (even machine independent) lines of code in the end but still I needed ages to get there. I however started getting more into the concept of GD2. Anyway, it's done. With this I was also able to further develop WMAN while still maintaining its platform independences as mode 64 patterns unify the mode 32 and 33 platforms. Now only the system palette is still on the "to do" list. By the way, I remember you having problems with the sprite cache, i.e. that it didn't notice the changes in the sprite edited by sprted. The same problem already exists in WMAN, if you try to define different colours for several scroll/pan bars this will fail as only the first version gets converted. What solution did you come up with? I'd like a clean way to flush the sprite cache but didn't find one so far. On a related note, is anybody up to redesign the standard sprites (namely arrow, lock, black window, keyboard input, no entry and probably window move and window resize sprites) in high colour? A picture of any format would be enough for me to convert it into code. Phoebus perhaps? :) Marcel
Re: [ql-users] GD2 and Hardware
On 13 Nov 2002, at 9:54, Malcolm Lear wrote: > > I was wondering if anyone can explain why programs such as > POV Ray only work on Qx0 machines. Mainly because they check whether they ARE running on such a machine, and, when not, just give up. The reason: The Qx0 on the one side, and QPC/QXL on the other side have incompatible High colour modes. The Qx0 has mode 33, QPC/QXL mode 32. In both cases, when you look at the data representing on pixel on the screen, the colour is coded on one "word" (16 bits). For mode 32, this is coded as: gggb rggg where for mode 33 this is coded as: grrr rrbw (where W is 1 if any two of the highest bits for the other colours are 1) In many applications that doesn't matter, since, when writing to the screen they just use the OS (SMSQ/E) which handles the "painting" onf th epixels correctly. Other software, however, such a POV, will write to the screen directly, this writing a word for each pixel into the screen memory. To avoid getting funny colours all over the screen, this software checks whether it runs on a machine that has the corresponding mode - if not, it gives up. Other software is a bit more intelligent (accomodating?) and paints the screen corresponding to the mode it runs in... > I can see that the > colours would be incorrect on other platforms such as QPC, > but don't understand why they refuse to run. With all this > talk of maintaining OS compatibility on different platforms > it seems strange that a lot of new software has major > problems dealing with something new like GD2. As there are only really 2 major high colour screen formats, and as there only thing one really has to do is some byte shifting, software could/should be written to take both formats into account - IF you really have to write to the screen directly! Wolfgang
Re: [ql-users] GD2 and Hardware - PovRay
Malcom, I normally use POV with QPC and Q60 and there is nothing strange , POV works great with both platform. I am just collecting a lot of wonderfull images and soon or later I will distribute it, the pity is that to render a complex image is taking a lot of time (10 to 30 hours). The POV version I use at the moment is the one you can find on Thierry G. web sites : gccPovray_exe. Ciao --- Malcolm Lear <[EMAIL PROTECTED]> wrote: > > I was wondering if anyone can explain why programs > such as > POV Ray only work on Qx0 machines. I can see that > the > colours would be incorrect on other platforms such > as QPC, > but don't understand why they refuse to run. With > all this > talk of maintaining OS compatibility on different > platforms > it seems strange that a lot of new software has > major > problems dealing with something new like GD2. > Perhaps its time for something like DirectX. > > Cheers > Malcolm > __ Do you Yahoo!? U2 on LAUNCH - Exclusive greatest hits videos http://launch.yahoo.com/u2
Re: [ql-users] Mouse on the Q40
On Wed, 13 Nov 2002 at 02:52:57, Phoebus Dokos wrote: (ref: <86B7VTLJHE1W86RNNH2XNNLONVQ31JI.3dd204d9@quantumcentral>) > >??? 13/11/2002 1:51:39 ??, ?/? "Wolfgang Lenerz" <[EMAIL PROTECTED]> ??: > >> >>On 12 Nov 2002, at 19:37, Phoebus Dokos wrote: >> >>> >>> I have a problem with the mouse. I am using a MS >>> compatible 3 button serial/PS/2 mouse (worked great with superHermes >>> and the regular QL using Sermouse) but isn't recognized by SMSQ/E... >>> is there anythin I need to run? (I tried sermouse but it doesn't work >>> with that either...) >>> >>I've always used a "normal" serial mouse. That has worked w/o any >>problems - what kind of Serial/PS2 converter does it have? >> >>Wolfgang >> > >It's using its own... as I've seen with most ps/2 - serial mice most of >them have to >use their own adapters as they differ from version to version... >However I really am afraid that the I/O just gave away, as the mouse >works as a >serial one everywhere (QL included). For fun I tested it with SerMouse >on the QXL >(without DOS mouse driver) and it worked > >I just hope it's not the I/O card as it is a slim one and nothing else >will fit in my >BookPC case :-( Why not make up a loop back cable from ser1 to ser2 to test the I/O card. Alternatively, you could link to another computer and open terminal programs each end, and type. The loopback is the best as it tests handshake as well. -- QBBS (QL fido BBS 2:252/67) +44(0)1442-828255 tony@.co.uk http://www.firshman.co.uk Voice: +44(0)1442-828254 Fax: +44(0)1442-828255 TF Services, 29 Longfield Road, TRING, Herts, HP23 4DG
[ql-users] GD2 and Hardware
I was wondering if anyone can explain why programs such as POV Ray only work on Qx0 machines. I can see that the colours would be incorrect on other platforms such as QPC, but don't understand why they refuse to run. With all this talk of maintaining OS compatibility on different platforms it seems strange that a lot of new software has major problems dealing with something new like GD2. Perhaps its time for something like DirectX. Cheers Malcolm
Re: [ql-users] Mouse on the Q40
On 13 Nov 2002, at 2:52, Phoebus Dokos wrote: > It's using its own... as I've seen with most ps/2 - serial mice most > of them have to use their own adapters as they differ from version to > version... I've had some trouble once with a mouse like that, a normal serial one then worked fine. > However I really am afraid that the I/O just gave away, as > the mouse works as a serial one everywhere (QL included). For fun I > tested it with SerMouse on the QXL (without DOS mouse driver) and it > worked You do these things for "fun"? :- > I just hope it's not the I/O card as it is a slim one and nothing else > will fit in my BookPC case :-( Yeah, ISA cards are starting to get hard to come by. Wolfgang
Re: [ql-users] Core software and Q60
Marcel Kilgus makes some magical things to make me read } } Unfortunately this way there's currently no high colour sprite format } in QXL/QPC I beg your pardon, but there is a high colour sprite format for QXL and QPC. How could sprted run on them otherwise ? It's just that mode 32 is not that mode... You need mode 33. Instead of R5G5B5W1 big endian, It's R5G6B5 little endian. (In both case, the data are 'hardware-ready') It also means that a high colour sprite using application which wants to run on both (Qx0 and QPC/QXL) must either double its sprite definition (so as to list both mode, quite a huge memory) or be able to convert from one mode to the other upon startup when on the alternative hardware. Or did I missed most of the context of your remark ?
Re: [ql-users] Mouse on the Q40
??? 13/11/2002 1:51:39 ??, ?/? "Wolfgang Lenerz" <[EMAIL PROTECTED]> ??: > >On 12 Nov 2002, at 19:37, Phoebus Dokos wrote: > >> >> I have a problem with the mouse. I am using a MS >> compatible 3 button serial/PS/2 mouse (worked great with superHermes >> and the regular QL using Sermouse) but isn't recognized by SMSQ/E... >> is there anythin I need to run? (I tried sermouse but it doesn't work >> with that either...) >> >I've always used a "normal" serial mouse. That has worked w/o any >problems - what kind of Serial/PS2 converter does it have? > >Wolfgang > It's using its own... as I've seen with most ps/2 - serial mice most of them have to use their own adapters as they differ from version to version... However I really am afraid that the I/O just gave away, as the mouse works as a serial one everywhere (QL included). For fun I tested it with SerMouse on the QXL (without DOS mouse driver) and it worked I just hope it's not the I/O card as it is a slim one and nothing else will fit in my BookPC case :-( Phoebus
