home *** CD-ROM | disk | FTP | other *** search
- SER
- NUM PROBLEM & FIX
- ----------------------------------------------------------------------
- 1029 - 9/30/89
-
- SYMPTOM:
- A couple people have reported that The Draftsman wouldn't
- recognize their VGA card, although MJVGA ran perfectly.
- PROBLEM:
- A real good question! The source code for the VGA test is
- identical in both programs!
- SOLUTION:
- I re-compiled The Draftsman using the same memory model as
- MJVGA. I also added an option which lets you attempt to run
- The Draftsman even if it doesn't see a VGA card. The
- Draftsman has always worked fine on my system & on the systems
- that I test it on. Therefore, I don't know if this fix will
- work or not. If you should experience this problem, please
- let me know.
-
-
- 1055 - The "official" release of Version 2.1
-
- SYMPTOM
- Someone with a VGA card reported that neither MJVGA nor The
- Draftsman would recognize his card.
- PROBLEM
- I dunno.... Strange VGA card maybe???
- SOLUTION
- He tried the above-modified Draftsman and said it worked fine
- after selecting "try anyway." MJVGA now includes this option.
-
- SYMPTOM
- If you select What's Left, then exit the What's Left screen by
- clicking the LEFT mouse button, the screen re-draws and either
- A) you return to the What's Left screen or B) you select some
- other menu item or tile.
- PROBLEM
- You're SUPPOSED to leave the What's Left screen by clicking
- the right mouse button, but in reality any button will get you
- out. Using the left button, however, was putting a "left
- button click" message on the stack. When the MJVGA game board
- returned, it saw this message & acted on it -- possibly taking
- you right back to What's Left.
- SOLUTION
- This was a simple one -- I just cleard the button stack after
- exiting the What's Left screen.
-
- SYMPTOM
- The computer locks up after the game board is displayed.
- PROBLEM
- This has only been reported once. The fellow corrected the
- problem himself by running MJVGA with the "D" command line
- parameter to disable the monochrome display routines. It
- seems that his computer didn't let MJVGA write to the "dead
- space" where a monochrome card should have been. It usually
- doesn't matter -- if there's no monochrome card, the data
- just "falls into the bit bucket" and causes no harm. But he's
- proven that in certain systems it DOES matter!
- SOLUTION
- Since the vast majority of people don't have dual monitor
- systems, I've changed the default from using the second
- monitor to NOT using the second monitor. Now, if you wish to
- use two monitors, YOU MUST START MJVGA WITH THE "D" COMMAND
- LINE PARAMETER!!!! This may inconvenience a few people, but
- will increase default compatibility to everyone.
-
-
- 1105 - 2/10/90 (Problem not fixed -- serial # indicates revision
- of this document.)
- SYMPTOM
- Someone reported that the abbreviated HELP command didn't work
- properly. The regular HELP menu appeared instead of just the
- number of moves left.
- PROBLEM
- MJVGA first checks the left mouse button to determine the
- command. It then expects to see BOTH the left AND right
- buttons pressed if you want the shortened HELP screen. If you
- release the left button before the computer can register that
- both are pressed, you'll get the standard HELP menu.
- SOLUTION
- I haven't fixed this one yet. It will be fixed in the next
- release, though. Until then, if you experience this, just
- hold down both buttons for a few extra moments to be sure that
- MJVGA sees them. You shouldn't experience this unless you
- either have a slow machine or are a fast clicker. I had to
- load down my 25 MHz machine with four background processes
- before it ran slow enough to let me see this problem.
-
-
- 1150 - 3/6/90
-
- SYMPTOM
- A couple people reported that they couldn't change "brush
- colors" in The Draftsman. Clicking on the color squares did
- nothing.
- PROBLEM
- This problem seems unique to Logitech's new Series 9 serial
- mouse. To date, all reports involved that mouse. Moreover,
- the Series 9 Bus mouse works perfectly! Only the serial mouse
- seems to cause this problem. I traced the exact cause to a
- timing problem. Briefly, I was asking the mouse which buttons
- were pressed before it knew. Consequently, it was telling me
- that NO buttons were pressed! My guess is that the bus
- mouse's hardware is faster than the serial mouse's for obvious
- reasons. The bus mouse was therefore able to register the
- buttons faster than the serial mouse.
- SOLUTION
- The solution was easy once I found the cause. I just execute
- a several-millisecond time delay before asking the mouse which
- buttons are pressed. This seems to give the rodent ample time
- to organize it's thoughts, even on my fast machine.
-
-
- 1234 - 6/1/90 The "official" release of MJVGA version 2.2
-
- SYMPTOM
- See the write-up for S/N 1105.
- PROBLEM
- See the write-up for S/N 1105.
- SOLUTION
- I've changed the mouse-check routine so that you'll get the
- abbreviated help whether or not the left button is still down.
- I have a suspicion, though that this problem may have been
- caused (at least in part) by the Logitech Series 9 serial
- mouse problem described above. If you should still experience
- this, PLEASE be sure to tell me whether you have that
- particular rodent or not.
-
-
-
- Note: The listed serial number is the first which contains a
- fix. All releases with later (ie larger) serial numbers will also
- contain the fix unless otherwise stated.
-
-
-