![]()
Auf Bitte melde dich an, um diesen Link zu sehen. findet ihr den neuen öffentlichen Beta-Treiber V 2.0.0.0 für die Catweasel-Controller MK3/MK4 für Windows 2000/XP.
Download hier: Bitte melde dich an, um diesen Link zu sehen.
Readme.txt:
---cut---
Catweasel MK3 and MK4 software update V 2.0.0.0
(Catweasel ISA code is not removed, please report if you have a system where you can test this!)
If you still have an old Catweasel driver installed, you have to remove it manually before installing this one:
The driver directory for Win2000 is (drive letter):\WINNT\system32\drivers
The driver directlry for Win XP is (drive letter):\windows\system32\drivers
For WinXP, it will be necessary to switch off some safety measures, otherwise you cannot delete the files. You might be successful by doing an un-install with the software/PnP manager, but updating the driver with the PnP manager is not possible. We haven't found a possibility to "tell" the PnP manager to actually replace the old with the new files. If you're trying it, it will report a successful update, but will leave the old files in place.
Delete the following files:
catwea2k.sys [base driver]
catdri2k.sys [floppy drive driver]
catkey2k.sys [Amiga keyboard driver]
catsid2k.sys [SID chip driver]
You might not find all of these files in your driver directory, depending on the used options of the controller.
Before installing the new driver, make sure to make a hard-reset. Either push the reset button at the right time (experts only), or shut down the computer completely and make a fresh power-up before you start installation. This will ensure proper reset of the MK4 hardware.
IMPORTANT NOTICE: Other than mentioned in the manual, Win 9x and Win ME drivers are no longer supported. If you still have one of those old systems, now is the time to upgrade. Developing drivers for systems that are not real 32-bit systems is way too expensive (time- and moneywise). We do like legacy computers, but not legacy stuff that should have been avoided.
There have been too many changes in the driver to list them here. The most important is probably that you won't see any more "blue screens" and that the floppy-passthrough (the "Kylwalda part") has been activated with this driver. Even with the Catweasel driver installed, you still have access to your A: drive. Only when the Imagetool is started, the A: drive appears empty to the computer. If you quit the imagetool, the A: drive becomes available again.
If you find a bug, please consult the "how to report bugs" textfile and gather as much information as possible, thanks a lot!
ReactOS.org people: Please contact us for driver compatibility with your operating system!
Developers: We'll publish some example sources on how to use the new functions, such as activating/deactivating the floppy-passthrough ("Kylwalda"), how to add new formats to the imagetool and so on. However, testing the new driver framework of this public beta release has priority at the moment, and it might be necessary to shuffle some things around before we can finalize the API.
There's still a lot of to-do's. One of them is to check the difficulties that a few people have reported on writing Amiga disks. It's been six bugreports from people who cannot read the disks in a real Amiga that the Catweasel has written. We're hoping that the driver framework flaws that have been corrected with this release cure most problems. More than 350 changes have been made in all of the four drivers. They could have caused data corruption, instable systems, bad communication between all the drivers and all kinds of funny things that you don't want a kernel driver to do. If you continue to have problems writing Amiga disks, please check that you're really using DD disks (or at least put Scotch tape over the HD-hole), and of course to use good floppy drives: We recommend Teac (not Teac OEM!), but Panasonic, Sanyo, Matsushita, Nec, Sony, Chinon, and most other brands also work fine. Three drives are known to be incompatible with the Catweasel line of controllers:
Mitsumi D359 series ("Newtronics", bad head alignment on brand new drives, interface flaws)
Teac drives with integrated flashcard reader (also made by Mitsumi)
Citizen floppy drives as used in Compaq computers (interface flaws)
Another loose end is power-saving and suspend mode functions. These Windows functions are hardly documented anywhere. Most books have paragraphs like "there is something like that, and it's very difficult to debug". True, especially without documentation about parameters of calling functions. If you have hints on where to find proper literature on this, your help is greatly appreciated. For now, all difficulties you might have experienced when shutting the computer down are solved, but suspend has to stay on the todo-list for now.
WinUAE support is very high on the list: The right/middle mouse button issue has already been addressed for the next internal beta release, and we also prepared the "true df0: emulation" in the driver. However, please report back if all known bugs are removed now, then we'll move on to adding new features.
The silence from internal betatesters of the past 30 days leads to the assumption that we're on the right path. Now put the driver to the test: Do all kinds of things that we might not have thought about and report back if you find a fault. If you see a so-called "bluescreen", please take the time to write down all numbers, it really helps us to find the cause. Also read the "how to report bugs" textfile in this archive. It'll save us all a lot of work.
greetings,
Tobias and Jens
---cut---
ams