@database Fix560.guide @node main "Fix560 documentation" @{b} immmmmmmm___. !@ ~~~~~~~~YW @ !@ @i ___ @i ,_. , ,_. Y[ '@******b__ i@@@@@` m@P W@@@W ][ @ WA*M[ i@@@@@! gZf~` ,W**M@@W ][ @. @[ ]W ,. @` Wf ,W! M@@. ]b V**M[ *M@@A ,WA@. iWs_ i[ _ W! dP @@[ ]@ ][i@@@mm VW.'Ms iA~~V@s ]b@@@s ]@ d@W_ @! Y@[ '@ ][ @[ @ VW.'MmA` iW! '~~*@@i @[i@@@@i ]@ ]@` @ @@@@! @[ i@ !W.'f WA` !@@ @[ 'V@@ ]@ ]@ @ Y[ @[ ]@ dA ,Wf Y@ @[ Y@ ]@[ ][ @ ]W @[ @ gA Mb . ]A @@. '@ ]@W @` @ ]@ Y[ @ gA gW. VW. W@. d! @@W_ ,g! ]@@W. ,W! @___/@ ][ @ ]P dPVW !W. V@@m_m! !@@@@@! M@@@@@! ****** !@mm@ 'MWdf Vb_m@! '*@* '*@* *@@*` '~~ 'f V*~ @{fg shine}v1.0 (March 31st 1998) by Renne Nissinen@{fg text}@{ub} @{" Mailware " link ware} Using and copying Fix560 @{" Introduction " link intro} What is this Fix560? @{" Requirements " link requ} What does Fix560 need? @{" Installation " link install} How to install @{" Usage " link usage} I wonder what this button does... @{" Fix560 FAQ " link faq} Frequently asked questions @{" Bugs " link bugs} Do we have an insect problem?? @{" Future " link future} Planned features @{" Author " link author} How to contact me @{" Misc info " link misc} Betatesters, technical info etc. @{" REALLY short " link realyshort} For those who don't read manuals @{fg highlight}Last minute information!@{fg text} I just saw an ad that was selling @{b}400 dpi@{ub} mouses. Does anyone have one of those? I don't know if Fix560 is useful on those, so please tell @{"me" link author}, if you've got one! @endnode @node realyshort "Fix560 documentation" @{fg highlight}@{b}Really short@{fg text}@{ub} If you have a 560 dpi mouse, you should use this program because without it, the mouse pointer will go to the wrong direction if you try to move it too fast. But if you don't have a 560 dpi mouse (the one you got when buying your Amiga probably isn't 560 dpi) then you don't need this program. If you aren't sure what kind of a mouse you've got, click @{"here" link mousetest} to see how you can check it. To install Fix560, just copy the program to your WBStartup drawer and double-click on its icon to start it immediately. If you're really lazy, just make sure that the "Test mode" button is OFF, and then click on Save and you don't need to worry about it any more (note that the window will always pop up on startup if you haven't saved the settings). If you want to know a bit more about Fix560, see @{"Usage" link usage}. @{fg highlight}@{bg fill}Don't forget to send me some mail!@{fg text}@{bg background} Otherwise I won't know if anybody uses Fix560! This is important! Here's my @{"address" link author}. @endnode @node ware "Fix560 documentation" @{fg highlight}@{b}Using and copying Fix560@{fg text}@{ub} Fix560 is mailware, which means that if you use it, you @{fg highlight}must@{fg text} send me some email, a postcard or something! That way I'll know that someone uses my program, and I can keep developing Fix560 and other good (?) programs for the Amiga. You can copy Fix560 to your friends freely, but if you are about to put this on your magazine's coverdisk then you must: - include the Finnish versions of the program and guide also! - @{"tell me" link author} about it I'd also appreciate it if you would send me a free copy of the issue, but I won't kill you if you don't ;) @endnode @node intro "Fix560 documentation" @{fg highlight}@{b}Introduction@{fg text}@{ub} The Amiga has counters in its hardware, that count how many dots the mouse has moved. A 560 dpi mouse is so accurate that the hardware counters can't always keep up with it, so the mouse pointer moves to the wrong direction if you move the mouse too fast. Note that this problem only occurs on the 560 dpi mouses, so if you know that your mouse is about 300 dpi (the standard mouse), you don't need this program and you can stop reading. If you're not sure what kind of mouse you have, click @{"here" link mousetest} for a little test. No program can magically make the counters bigger and better, but this one will monitor the mouse movements and if it detects that the mouse is probably going too fast, it switches the direction. Therefore you can move the mouse almost twice as fast without any problems. @endnode @node requ "Fix560 documentation" @{fg highlight}@{b}Requirements@{fg text}@{ub} Fix560 needs OS3.0 and reqtools.library 2.9 (v38, not included) and only about 10kB of memory. That's all! (except that YOU are also required to mail @{"me" link author}! :) @endnode @node mousetest "Fix560 documentation" @{fg highlight}@{b}Testing your mouse@{fg text}@{ub} If your mouse has 3 buttons and in the lower left corner there's a text "Wizard developments" then it quite certainly is 560 dpi :) If you still aren't sure what kind of a mouse you've got, then read on. First of all, if you haven't already started Fix560, then start it, make sure that the "Test mode" is ON, and hold down the left shift (this disables the fix mechanism until you let go of the button). Then start moving your mouse in a circle, so that you can see the pointer on the screen all the time (you might want to set the speed to 1 in the Input Preferences). Move it faster and faster, until the pattern isn't a circle any more but an almost random pattern. If that happens, you definitely have a 560 dpi mouse and you need Fix560 :) And now, still moving the mouse just as fast, let go of the shift. It takes only a little moment and the pointer should start going the right way (note that this delay occurs only because you enabled the fix mechanism when the mouse was already going too fast; if you have it enabled all the time it gets fixed before it even goes wrong :) If letting the shift up has no effect, you should hold it down again and slow down so that you move the mouse only a little faster than the speed where the pointer starts going crazy, and now try letting go of the shift. (of course, there IS a limit to the speed where Fix560 can fix it :) But if you move your mouse so fast that the mouse mat starts to smoke and the pointer still goes the right way, you probably have a 300 dpi mouse or so, and you don't need Fix560 so you can stop reading now and forget about it. @endnode @node install "Fix560 documentation" @{fg highlight}@{b}Installation@{fg text}@{ub} Installing Fix560 is very simple; just copy the program to your WBStartup drawer. You should also start it manually after that and see what it's all about. Note that the window will pop up on startup until you save the settings, so remember to save 'em when you're done testing! :) @endnode @node usage "Fix560 documentation" @{fg highlight}@{b}Using Fix560@{fg text}@{ub} First of all, if you decide to use Fix560, you @{fg highlight}must@{fg text} send @{"me" link author} some mail! I won't make any bug fixes or anything if I don't get any mail, plus I would also @{fg highlight}really@{fg text} like to know who and where is using Fix560 :) Please, and I mean pleasepleasepleaseplease, @{fg highlight}@{bg fill}send me some mail!!!@{fg text}@{bg background} At least tell me if you noticed any changes in the way your 560dpi mouse moves or not. This is very valuable information to me, and besides, I like getting mail! :) Just click @{"here" link author} and stir something up ;) Phew.. :) Now on with the show :) Using Fix560 is very simple, since you just install it and use your mouse :) But there are a few settings. If you enable the "Test mode" from Fix560's window, you can test its effect by holding down the left shift (this disables the fix mechanism until you let go of the button). Now if you move the mouse so fast that the pointer goes crazy (try moving it fast in a circle), you can let go of the shift and the mouse pointer should start going the right way. There's a little delay between working and not working, but it's because you enabled the mechanism when already moving the mouse. If you keep it enabled all the time, there will be no delay :) You can also alter the fix mechanism's trigger and treshold values. When you are moving the mouse, the program checks if the mouse pointer has moved more than "trigger" pixels in the current display frame (usually from 1/50 secs to 1/85 secs long). Nothing happens yet, but in the next frame it checks if the mouse pointer has moved more than "treshold" pixels to the opposite direction. This is what happens when you move the mouse too fast, so the program thinks that it's not what you wanted and reverses the direction so now it has been fixed :) Anyway, you probably shouldn't dabble with the values because it's hard to get them to optimum performance; if fast straight movement is fixed very well, then fast back-and-forth movement isn't fixed so well. Especially, if you don't understand what I've just told you about the way Fix560 fixes the movements then you should leave the values to the default 60 and 40, or maybe try if 50 and 50 makes any difference. Oh, by the way, the Mouse Speed setting in the Input Preferences doesn't affect what the trigger and treshold values should be, except that Fix560 probably won't be needed if the speed is 3, since you won't have to move the mouse so fast :) (if you @{fg highlight}@{bg fill}really@{fg text}@{bg background} want to know more then you can contact @{"me" link author} :) @endnode @node faq "Fix560 documentation" @{fg highlight}@{b}Frequently asked questions@{fg text}@{ub} Nobody has asked me anything since this is the first version :), but I can imagine a couple of questions you might have, especially if you haven't read this guide very carefully... :) - Does the Mouse Speed setting in the Input Preferences affect what the treshold and trigger values should be? - Nope :) You just probably won't need Fix560 at all if you use speed 3. - Why the hell does the window always appear after booting the machine?? - You have to save the settings to make it go away :) Or, if that doesn't help, check that the tooltype CX_POPUP is NO. Also, the prefs file must be in ENV: so if your startup-sequence is so screwed up that there's no ENV: (or if the contents of ENVARC: aren't copied to ENV: at startup) then you'd better format your HD and install everything again =) - How can I get the window to open?! - Start Exchange, select Fix560 and click on "Show Interface". You could also press the hotkey defined in the tooltype CX_POPKEY, or run Fix560 again. - Do I really need Fix560? - If you have a 560 dpi mouse, then yes (well, you don't @{b}need@{ub} it but it will help :). If not, then no. - I'm not sure whether I have a 560 dpi mouse or not...? - Well, if you have already done the @{"test" link mousetest} and you're still not sure, then my advice is that if you haven't noticed the mouse pointer going to the wrong direction, then you don't need Fix560. - Since I need Fix560, did I waste my money when I bought my 560 dpi mouse? - I don't think so. As for myself, I used to have a similar looking mouse but it broke down and I couldn't find another one so I bought this one, and I don't regret it. It fits in my hand perfectly etc. Plus, now I've got three buttons, and the machinery is very good... an excellent mouse, I must say, and after all the problem IS in the Amiga... :) To be continued... :) @endnode @node bugs "Fix560 documentation" @{fg highlight}@{b}Bugs@{fg text}@{ub} I don't know any bugs in Fix560, but I can tell you that I haven't tested Fix560 with Enforcer since my gvpscsi.device causes Enforcer hits :( But the @{"betatesters" link misc 20} didn't report any Enforcer hits so there probably aren't any :) @endnode @node future "Fix560 documentation" @{fg highlight}@{b}Future plans@{fg text}@{ub} I don't think that Fix560 v1 needs a lot of work any more, but I have thought a bit about a better fixing mechanism that would completely "cure" the problems, even when moving the mouse as fast or as suddenly as you can. But it will probably need a lot of work so you'll just have to hang on for now and wait for Fix560 v2 :) But of course there are some things I could fix/change before that, and I will think about every suggestion you send me. Here are some ideas I've come up with that might be implemented in future versions: o prefs to the icon's tooltypes instead of this 20-byte file in ENVARC: o save window position (except if...) o maybe remove the window? ->smaller executable and less work for me :) o I don't know? Anything sensible that you can think of :) Mail any ideas, suggestions, bug reports or anything to @{"me" link author}. @endnode @node author "Fix560 documentation" @{fg highlight}@{b}The author@{fg text}@{ub} I am Renne Nissinen, from Finland :), and if you want to comment something, report bugs, tell me your ideas or @{u}use this program@{uu}, then send me a postcard, email or anything (no mailbombs, please 8). Also, if you are sure that you have a 560dpi mouse and Fix560 just doesn't make any difference, then tell me about that, too! :) The addresses are: Email: rennex@icon.fi (if that doesn't work, then try renne.nissinen@mbnet.fi) Snailmail: Renne Nissinen @{bg shine} @{bg fill} @{bg shine} @{bg background} Koivukylantie 4 K @{bg shine} @{bg fill} @{bg shine} @{bg background} 01300 Vantaa @{bg fill} @{bg background} Made in Finland! :) Finland @{bg shine} @{bg fill} @{bg shine} @{bg background} (Europe :) @{bg shine} @{bg fill} @{bg shine} @{bg background} Just go ahead, I need to know if anybody uses this program, and I also like getting mail :) @endnode @node misc "Fix560 documentation" @{fg highlight}@{b}Miscellanous information@{fg text}@{ub} Fix560 has been tested on five different Amigas and four different 560 dpi mouses, and on every one of them Fix560 worked and was of help, so I think that it is safe to say that Fix560 really works :) It didn't crash the machines either, as you probably thought... :) The machines on which Fix560 was tested were: - A1200, 060/50, OS3.0 - A1200, 030/50, OS3.0 (two of these) - A4000, 040/30, OS3.1 - A1200, 060/50, OS3.0+WB3.1 Unfortunately, we had only Wizard's 3-button 560dpi mouses, so Fix560 hasn't been tested on any other mouses, but why should they work any better without Fix560?-) If you have some other kind of 560dpi mouse, then tell me about it @{b}when@{ub} you mail me, and also tell me if Fix560 helped anything :) @{fg highlight}@{b}The betatesters@{fg text}@{ub} List of betatesters: Olli-P. Kaikuaho Timo Sievänen Simo Koivukoski Thank you very much; I couldn't have published Fix560 if you hadn't told me that it works! :) If you suddenly feel the urge to become a betatester for future versions, contact @{"me" link author} :) @{fg highlight}@{b}Compiler information@{fg text}@{ub} Fix560 was assembled on March 31st 1998 at exactly 18:06:25 (Finnish time :). Here's all the text that the assembler printed, in case you want to know: PhxAss MC680x0/68851/6888x Macro Assembler v4.37 Copyright 1991-97 by Frank Wille Pass 1 Pass 2 00 No errors. 16763 lines in 9.68 sec = 103902 lines/min. Global symbols: 5307 Local symbols: 98 Bytes gained by optimization: 790 Code: 1 section(s) 6060 bytes Data: 1 section(s) 548 bytes BSS: none @endnode