ÎÎÎ Fri, 31 Dec 2004 00:51:32 +0000,Î(Î) Tony Firshman <[EMAIL PROTECTED]> ÎÎÏÎÏÎ/wrote:
On Thu, 30 Dec 2004 at 22:21:00, Rich Mellor wrote: (ref: <[EMAIL PROTECTED]>)
<snip>The other problem I have come across is that once past this hurdle, people trying to install on a system with a SuperHermes system think that they can put the boot disk in FLP1_ and forget that they need to load the keyboard drivers first... (then complain the installer will not respond to any keys).
Tony - if people upgraded to a full SuperHermes instead of SuperHermes lite, is it possible to load the keyboard drivers automatically, or is the only way of doing this by adding them as a module to smsq/e (which people also forget to do when they upgrade to the latest smsq/e).Surely this could be loaded via the boot program after smsq/e is loaded.
Well Rich is right... even the most experienced tend at times to forget that they have a superHermes (it works THAT well :-)
Trouble is that when you tell people to run an installer from the boot on the supplied disk, they put the disk into the disk drive and reset the system !! They forget about the need for a SuperHermes driver - we could supply it with the installer disk, but the problem is that what happens if the user uses a different keyboard interface??
I have no problem with superHermes drivers being included as standard with such auto-installers or smsq/e. After all the hardware has not been cloned (as far as I know). If anyone does clone the hardware, then good luck to them (8-)# . I would be -very- interested to see how large it might be.
Is there any reason why the smsq/e for Gold Card / SGC could not include the SuperHermes module by default. The current config option (about the ABC keyboard) could be amended to say "Type of keyboard attached : ABC / SuperHermes / Unknown" and then if the user configures Superhermes, run the IPCEXTs initialisation code for the smsq/e configured country.... (knew that post configuration routine pointer would come in handy some day).
As a Keyboard 90 maybe? :-D
Maybe it should be added to smsq/e as of normal - not sure how we can put it with an auto-installer in case the user jas another keyboard interface - or is there a simple test we could put in the boot program to check if superhermes is present, in which case, load the ipcexts. No idea if it would be a problem if they use ABC Keyboard or Keyboard 90 and we just installed the ipcexts anyway...
I tend to load the sH drivers everywhere as I never know when I am going to need them. Luckily they are a great piece of software and as such they never interfere with anything!
See above?
I personally use the ROM1 approach although I recommend to people to download that little basic program from your website that can make a module out of them (and of every rommable code they have) and "Stick" it (sic) at my SMSQ/e. That grows the executable but makes for an incredibly efficient boot file (ie 10 IPCMOUSE) :-)
Yes, ok for those with a romdisq, but not every user has one...
<<cut>>
One problem though is, of course, that there are different language drivers.
You call THAT a problem? I wish SMSQ/e had half the keyboard drivers the sH solution has... btw have I sent you my greek sH driver?
Would not be a problem if the necessary module was linked into the main smsq/e initialisation code at configuration time.
More of a problem if we had to include ipcexts in the boot file for the installer and also on non smssq/e systems of course
-- 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
