ppgrainbow

Thanks for the link to the article in question. I appreciate it. It seems that the PS/2 wheel mouse and the Toshiba AccuPoint device doesn't like to get along with each other.

Thanks for the help. I appreciate it. I'm planning on getting a second Mitsumi Standard Scroll mouse for this desktop computer this Christmas. At this time, I can only enable to AccuPoint mouse if I change the setting on the Pointing Devices in the BIOS to Simultaneous. If I get a camera ready, I'll post a photo of what the AccuPoint mouse looks like soon. For the time being, I'm about ready to head for bed.

Okay, folks! I think I found the problem and it's not related to operating systems at all...it's one of the settings in the BIOS setup! If I press ESC or use a utility called TSETUP.EXE (which must be done from the MS-DOS prompt), it will take me into the CMOS setup. In the first page, there are features that will change how the laptop operates. In the OTHERS section under Pointing Devices, there are two options available: 1. Simultaneous 2. Auto-Selected If I select Simultaneous, the Toshiba AccuPoint mouse is active along with the AccuPoint left (on the top) and right (below it) mouse buttons are active. However, this will disable the ability to use the scrolling feature on the PS/2 mouse. Thus, the Microsoft IntelliPoint 4.01 software treats the wheel mouse as a regular two button PS/2 mouse. If I select Auto-Selected, I will not be able to use the eraser feature on the Toshiba AccuPoint mouse and its features. This causes the scroll mouse feature to work correctly. Sadly, this is most likely a design limitation in Toshiba laptops from the mid-to-late 1990s. If I were to set the Pointing Device to Auto-Selected, I wished that I found a way to get the AccuPoint mouse working again. Thoughts anyone?

Alrighty. I'll think about zeroing out the partition completely.

Alrighty. I'll probably use FDISK to delete the partition and recreate it. If I get the wheel mouse working, I'll let you know. But I won't do that before I get the 1.2 GB hard drive replaced.

Yes. The drive is installed in a single partition. The old 1.2 GB hard drive is going to be replaced with a 4.3 GB version and I will most likely have to start over. The backup copy of the 1.2 GB hard disk is stored in a hard disk image under MK2720FC.vhd. Driver corruption problems causes a lot of problems lately. If that still doesn't work, I don't know what to say.

Yesterday, I had to switch PS/2 mice and Win2K detected the Mitsumi Standard Scroll Mouse out of the box and when I plugged in the old Hewlett Packard PS/2 wheel mouse onto the Tecra 720 CDT laptop, it wouldn't detect the scroll wheel. I installed IntelliPoint drivers (both version 4.01 and even version 2.2) and for some reason, it failed to detect the scroll wheel on the PS/2 mouse. No matter how hard I try, Windows 95 would detect the driver as a standard PS/2 mouse and not a standard PS/2 wheel mouse. As far as I know, the Tecra 720CDT laptop only has support for the AcuPoint Integrated mouse pointer and PS/2 mouse...and I've been thinking that the BIOS might not be capable of detecting the wheel on the PS/2 mouse. I could be wrong. Edit: Alright, I made little progress here. I reinstalled Microsoft IntelliPoint 4.01 and managed to get the mouse to detect it as a "Microsoft PS/2 Mouse with Wheel (Intellipoint)" and still in the Button settings, the device that is connected is still being detected as either a Microsoft Mouse or a Basic Mouse. However, when I reboot, Windows 95 keeps detecting the mouse as a Toshiba AcuPoint. What could be wrong here. I've been trying to find registry keys and files that cause the Toshiba AcuPoint driver to be loaded all of the time, but it hasn't been any help either.

I did install Microsoft IntelliPoint 4.01, selected the Wheel Mouse and I checked the Control Panel in the Mouse settings and it only detected it either a Microsoft Mouse or a Basic Mouse. What could I be doing wrong here? Update: I even tried out the Pilot Mouse Wheel Scroll v1.0 driver and it failed to detect the middle button mouse/scroll wheel. Speaking of the middle button mouse/scroll wheel, it's not a ordinary one. Instead of scrolling up and down with the wheel. Pressing the middle button up or down scrolls the page up or down. If I didn't make any sense, let me know and I'll explain more.

For some reason, going into Safe Mode and attempting to remove the mice from the Device Manager didn't work. I got a error saying that the registry is corrupt and had to be restored from a good backup copy. I'll try to pull up a screenshot if I can explain the reason more.

The problem is WHICH reason. Does that mouse middle button work on another PC with another (more recent) OS? Or is it DOA? Did you install the software correctrly? Refer to this doc: http://sysdoc.doors.ch/MITSUMI/1/ScrollUK.pdf Did you have previously anothe mouse driver installed? Do you see any device with a question mark in device manager? jaclaz The scroll mouse button works on this PC correctly. As for the Tecra 720 CDT PC, I previously had another PS/2 mouse installed and it was just a standard PS/2 mouse. I had to do the following: 1. Reinstall the Mitsumi PS/2 scroll mouse. 2. Disable the other PS/2 compatible mouse as it causes a IRQ conflict with the Mitsumi PS/2 scroll mouse. 3. Delete (or rename) the msmouse.inf file in the C:\WINDOWS\SYSTEM directory. 4. Re-enable the Mitsumi PS/2 scroll mouse and shut down. The Mitsumi PS/2 scroll mouse is working correctly, but still for some reason, the middle mouse button and scroll buttons still don't work. I'm sorry that my grammar is not perfect, but what are the additional steps that I need to take to get the middle mouse/scroll button working?

Okay, last weekend, I bought a Mitsumi Standard Scroll Mouse (PS/2) from eBay for the Toshiba Tecra 720CDT laptop with Windows 95 OSR2 and for some reason, the middle button/scroll bar doesn't seem to work. I even downloaded the drivers found in the mtm0413.zip file and it wasn't any help. The mouse is still functional, but I would like to take advantage of the scroll wheel and middle mouse button under Windows 95, which isn't supported by default. The model number of the PS/2 mouse is ECM-S5002, by the way. How can I get the scroll mouse/third mouse button to work under Windows 95?

I would like to point out that Quicktime 5 would work if Hardware Acceleration was set to full. I have the VM set to 64 MB and Qt5 eats up at least 32 MB of memory. To make QuickTime 5 work, I had to go to right click Properties where it will display the property settings. Then go to Settings > Advanced Properties > Performance and set the hardware acceleration to Full. Gah, I'm dumb sometimes. I need to set the hardware acceleration to Full on the Tecra720CDT laptop, but I probably won't do that until after I get the hard drive upgraded.

For some reason after I reinstalled Windows 95 under Virtual PC 2004, I managed to install QuickTime Player 5.0.5 (the latest supported version under Windows 95) and when the installation gets done, it refuses to start up correctly. When I hit the right control-delete buttons (control-alt-delete), I found that the task manager reports that QuickTime player (quicktimeplayer.exe) does not respond. Furthermore, I cannot even properly uninstall QuickTime 5.0.5. QuickTime Player 5.0.5 worked under a existing installation of Windows 95 under VMware and I found that reinstalling it can become a serious limitation. I could be wrong. Does anyone have any ideas on how to get QuickTime Player 5.0.5 working again?

I installed Echofon 2.3, a popular Twitter client add-on and while it loaded, it did not work correctly...if not at all. The reason is that the DLL in the \platform\echofonsign.dll file uses EncodePointer and DecodePointer, the two key MSVC++ 2010 CRT entry point DLLs that do not exist on versions of Windows prior to Windows XP SP2; plus almost 963 KB worth of code (including support code for Windows 2000) was removed too. In my opinion, Echofon shouldn't be even offering later versions of their product (after version 2.2.2) that does not work on this OS! The last version of Echofon that will work on Firefox running on Windows 2000 (and Windows XP before SP2) is version 2.2.2. Until there are unofficial builds, hacks and workarounds, let me know. Echofon 2.2.2 can still run on Firefox 8 and later, if you do the following: 1. Download Echofon 2.2.2, extract the echofon_for_twitter-2.2.2-fx.xpi using 7-zip into a temporary directory. 2. Open the install.rdf file using Notepad. 3. Where it says "<em:maxVersion>8.0a1</em:maxVersion>", change it to the highest supported version of Firefox that will run on Win2K. I'm sorry that my grammar isn't all that perfect, but the good news is that Adobe Flash Player 11.1.202.55 came out today, installed it and found that it still works on Win2K too...even on Internet Explorer 6 SP1 as tested through VMware Player. Plus Firefox 11 recently entered Nightly and Firefox 10 moved to Aurora. Also, there is a beta version of Flash 11.2 that has been out since late last month. It would be great to test Firefox 10 Aurora, Firefox 11 Nightly an Adobe Flash 11.2 beta to see if they will still work on Win2K or not. What do you think?

Thank you so much!

Holy crap, this thread hasn't been updated in a while. I recently tested out the final version of Adobe Flash 11 (runtime version 11.0.1.152) on Windows 2000, both through a Windows 2000 VM (under VMware Player) and on the host PC and it still works. By using the Dependency Walker feature, I found that one of the files in Flash11c.ocx (one of the files attributed to the Flash 11 installation) is missing entry point function called WNetRestoreConnectionA in the MPR.DLL file. However, that does not prevent Flash 11 from working on Win2K. I don't know if Flash Player 11.1 (if it is planned) will even work correctly on Win2K or not. Also, has Firefox 9 Aurora and Firefox 10 Nightly been tested on Win2K yet? If there is any confirmation on this, let me know.

Hey there, everyone! I've been lurking around the forums for a while and I find that this website is a very helpful resource. I'm gonna see what's going on here.