#A2088/DOS50/AMOUSE/Crash
14 messages in this thread
Don:
Thanks for the advice, it makes sense. After many frustrations I
decided to go for the big bananna. I reformatted the hard drive totally,
upgraded to JANUS 2.0, upgraded to MS-DOS 3.3, made a 10 MEG autoboot
partition with MAKEAB, and then upgraded to MS-DOS 5.0.
After several years of running Wordperfect from 2 360K drives, I now
have an autoboot harddrive with DOS 5.0…WOW!!! It did however take 3 low
level reformats of the hard drive and lots of work.
ONE QUESTION REMAINS. DOS 5.0 seems to choke on AMOUSE.COM from Janus
2.0. It says I do not have the most recent mouse driver, contact my
supplier. Any idea how to get AMOUSE to work with DOS 5.0 so I can use my
Amiga mouse on the shell ??? Thanks for any help.
– via Whap!
Bill,
I haven't used DOS 5, so I have no idea if amouse will/won't or
can/can't be configured properly for it. Perhaps a call to Commodore to
ask them might be in order.
My *guess* is that if the program says you need a newer
version…that may in fact be true. Unfortunately, I don't believe there
is a newer version of Amouse available. I guess another good reason to
call Commodore and ask them.
Don
Don, I haven't used Amouse with DOS 5 because of my SOTA, but Commodore
does have DOS 5 in house in West Chester and hopefully is testing it. Also,
you may remember that Andy had indicated they were doing some testing
involving Amouse, SOTA, etc; and that they had a newer bios chip.
Ron
Ron:
Do you have any other ideas of what might make AMOUSE work with the
A2088 and Janus 2.0, using DOS 5.0 ? Or any idea who I should call at C=
to find out more info ? Thanks for any input.
– via Whap!
The only people who have the answer to that are at CATS, so we have to wait
for them to answer it. For a while one of them was showing up on one of
the forum's, but not any more. All we know is that 'they're working on
it'.
BTW, there is one thing you can try, though I doubt it will work; try out
SETVER for AMOUSE.
Ron
I heard on usenet that you can just tell DOS 5.0 to use the old mouse
driver anyway and that it then worked ok. I don't have dos 5.0 so I can't
comfirm this.
Tim
Ignore the message from DOSSHELL that says that the mouse driver is not
recent. It works just fine and the message only pops up once unless you
change your screen resolution.
John
John:
I followed your advice on how to get Amouse working with DOS 5.0 on the
A2088. I have Amouse running on the Amiga Side and Amouse.Com on the
MS-DOS side. My startup sequence on the A2088 displays that Amouse version
1.5 is running on the IBM side. When I run the program but do not click
Left-Amiga-P my traditional Amiga mouse pointer moves around the screen
just fine. After I hit the Left-Amiga-P combo the pointer freezes on the
screen and no other pointer moves on the screen. I had incorrectly assumed
that this meant the mouse was not working.
It seems now that the mouse is working just fine on the IBM side. Only
one problem. The pointer is invisible. I have invoked all DISPLAY modes and
all COLOR combinations, but the pointer is still invisible (the amiga
pointer remains visible but frozen). Using a mouse with an invisible
pointer is possible, but …..challenging. By the way I am using AMOUSE 1.5
if that matters.
Also, I note that I am not getting the "recent mouse driver" message
anymore. I'm not sure why.
Any ideas on how to improve this situation ????
– via Whap!
Bill,
I got the same mouse driver message from DOS 5.0. I've yet to see any
problem using amouse, though.
David
– via Whap!
David:
Since your Amouse is working with DOS 5.0, I would very much like to ask
you to look at what I've done to see if you can spot any obvious problems.
I have an A2000 with a GVP Impact controller with 2 Megs additional running
an St-157N-1. I have an A2088 with an AST Six Pack Plus with aditional
memory up to 640K. I created a 10 MEG partition,DH2:, on my hard drive. I
used MAKEAB to make a 10 MEG IBM bootable drive for the A2088. An external
A1010 and A1020 drive alternately hooked to the BB. I have a GoldenImage
Mouse, and an original Amiga2000 mouse, both show identical problems.
I did have some minor problems putting Janus 2.0 on my HD so I copied
the files directly, everthing else has seemed to work. My PC Prefs is set
for RAM=D000 and only COLOR ON (My A2088 jumper is set to color on also.)
Everthing I run on the BB works like a champ except the Amouse.
In my Amiga s-s I have "RUN >NIL: SYS:PC/PCDISK" and RUN >NIL:
SYS:PC/AMOUSE" after binddrivers. In AUTOEXEC.BAT I have
"C:\JANUS\AMOUSE.COM". I get a message in the blue Amiga border to the PC
screen which says something like "Amouse is active on the XXX port". During
the DOS 5.0 start-up I get a message that says something like "AMOUSE 1.5
is installed". I used to get a DOS shell message that said I did not have
the latest driver, but I do not get that message now.
When I start the PC side, the standard Amiga mouse pointer is
functioning just fine. I then double click on the screen to get rid of the
Amiga scroll gadgets, that works just fine. I then hit left Amiga-P to
change mouse ports and the AMiga pointer freezes at whatever location it
was in. No alternate image appears. I have carefully examined the PC
screen but find no cursor moving around. I do have a blinking yellow
underline in the top left corner that appears to be a cursor, but it never
moves. I am set up in DOS 5.0 text mode with the default colors, but I
tried the other text modes, and the graphic mode without any change. ALso,
[ MORE ]
[ continuation ]
I have the standard Amiga monitor (A1080??) with no flicker fixing type
stuff.
Please let me know if you spot any obvious errors, or can think of
anything to try. I am out of ideas by now.
– via Whap!
Bill,
My *memory* of using a mouse with MS-DOS is that unless you're
running a program that uses the mouse…you won't get anything on the
screen. I could easily be wrong on this…but that's the way I remember
it. The program draws and uses the mouse…it's not inherent in the system
(like the Amiga) so there's nothing to be seen in the MS-DOS shell.
But let me go check real quickly under MS-DOS 3.2
Yup…just tested it. No mouse is visible until you run a program
that uses a mouse. At least that's the way it works under MS-DOS 3.2.
Don
MS-DOS 5.0 does use a mouse in the shell.
Bill,
I've got an A2286 bridgeboard with a separate HD on the PC side. My setup
is a bit different than yours, since I'm not using a janus partition on my
Amiga drive. I'm also using a separate VGA card and monitor. The presence
of the VGA card affects my ability to run on the Amiga screen and might
also explain why I can see the mouse pointer and you can't. The one
obvious difference that I see in our settups is that I have not disabled
the mono screen. Offhand, I can't see why that might make a difference, but
I thought I'd mention it anyway.
Here's how my setup works:
With the normal color scheme for the DOSshell, the mouse pointer is a cyan
colored block cursor. It does show up on my screen whether or not the
mouse is actively controlling it. It's a bright CYAN block on the vga
screen, but not on the Amiga emulation. On the Amiga screen, it becomes
invisible when the BG color is cyan. With the standard color scheme, only
the menu line at the top and the prompt line at the bottom are cyan.
I'll try a bit more experimenting and let you know if I discover anything.
Hope this helps, 8)
David