Update 3 scroll wheel no longer working

A forum for general AmigaOS 4.x support questions that are not platform-specific

Re: Update 3 scroll wheel no longer working

Postby mrdarek » Wed Aug 31, 2011 9:11 pm

USB2 enabled, bootmouse disabled, poor esperanza mouse detecting 4 times with success but too long:


I: [21:18:42] USB stack | | ==========
I: [21:18:42] USB stack | | USB System Software Task started
I: [21:18:42] USB stack | | Starting HCDs...
E: [21:18:43] USB stack | New Fkt | fkt: 0x5FE091F0 = Level -1
E: [21:18:43] USB stack | New Fkt | fkt: 0x5FE09290 = Level 0
I: [21:18:43] EHCI Controller Task Unit 0 | EHCI | Another driver seems to use the PPC460ex USB hardware. Sending shut down notification.
W: [21:18:43] OHCI Controller Task Unit 0 | OHCI | Received request to shutdown unit 0.
W: [21:18:43] OHCI Controller Task Unit 0 | OHCI | Releasing lock for unit 0.
I: [21:18:43] EHCI Controller Task Unit 0 | EHCI | Successfully locked PPC460ex USB hardware.
E: [21:18:43] USB stack | New Fkt | fkt: 0x5FE09330 = Level -1
E: [21:18:43] USB stack | New Fkt | fkt: 0x5FE093D0 = Level 0
I: [21:18:43] USB stack | | ...HCDs started.
I: [21:18:43] USB Fkt Init | Init Fkt | Fkt 0x5FE09290 is {Vendor: 0x0000, Product: 0x0000, Class: 09.00}
I: [21:18:43] USB Fkt Init | Init Fkt | Fkt 0x5FE093D0 is {Vendor: 0x0000, Product: 0x0000, Class: 09.00}
I: [21:18:43] USB Fkt Init | Init Fkt | Fkt 0x5FE09290 initialized
I: [21:18:43] USB Fkt Init | Init Fkt | Fkt 0x5FE093D0 initialized
I: [21:18:43] hub.usbfd | HUB | Hub "Rear Roothub (ohci.usbhcd/0)" has TT thinktime of 8 full speed bittimes and protocol 0
I: [21:18:43] hub.usbfd | HUB | Hub "Rear Roothub (ehci.usbhcd/0)" has TT thinktime of 8 full speed bittimes and protocol 0
I: [21:18:43] hub.usbfd | HUB | All ports are empty
I: [21:18:43] hub.usbfd | HUB | Device found on port 1 of hub "Rear Roothub (ehci.usbhcd/0)".
I: [21:18:43] hub.usbfd | Hub port | Device at port 1 of hub "Rear Roothub (ehci.usbhcd/0)" is high-speed.
E: [21:18:43] USB stack | New Fkt | fkt: 0x5FE095B0 = Level 1
I: [21:18:43] hub.usbfd | HUB | Device on hub port 1 successfully added.
I: [21:18:43] EHCI Controller Task Unit 0 | EHCI | Port 0 is not in reset state.
I: [21:18:43] hub.usbfd | HUB | Driver Running
I: [21:18:43] USB Fkt Init | Init Fkt | Fkt 0x5FE095B0 is {Vendor: 0x0424, Product: 0x2517, Class: 09.00}
I: [21:18:43] USB Fkt Init | Init Fkt | Fkt 0x5FE095B0 initialized
I: [21:18:43] hub.usbfd | HUB | Now configured to use multiple TTs
I: [21:18:43] hub.usbfd | HUB | Hub "" has TT thinktime of 8 full speed bittimes and protocol 2
I: [21:18:44] hub.usbfd | HUB | Device found on port 1 of hub "".
I: [21:18:44] hub.usbfd | Hub port | Device at port 1 of hub "" is low-speed.
E: [21:18:44] USB stack | New Fkt | fkt: 0x5FE096F0 = Level 2
I: [21:18:44] hub.usbfd | HUB | Device on hub port 1 successfully added.
I: [21:18:44] hub.usbfd | HUB | Device found on port 2 of hub "".
I: [21:18:44] USB Fkt Init | Init Fkt | Fkt 0x5FE096F0 is {Vendor: 0x1C4F, Product: 0x0003, Class: 00.00}
I: [21:18:44] USB Fkt Init | Init Fkt | Fkt 0x5FE096F0 initialized
W: [21:18:44] USB FD fkt start | USBFktGetCfgDescriptors | Error reading config dsc from Fkt 0x5FE096F0
E: [21:18:44] USB FD fkt start | USBFktGetCfgDescriptors | Failed to read config from Fkt 0x5FE096F0 - error -36
E: [21:18:44] USB FD fkt start | FD launcher | Failed to read CfgDsc
I: [21:18:44] hub.usbfd | Hub port | Device at port 2 of hub "" is full-speed.
E: [21:18:44] USB stack | New Fkt | fkt: 0x5FE09790 = Level 2
I: [21:18:44] hub.usbfd | HUB | Device on hub port 2 successfully added.
I: [21:18:44] USB Fkt Init | Init Fkt | Fkt 0x5FE09790 is {Vendor: 0x413C, Product: 0x1005, Class: 09.00}
I: [21:18:44] hub.usbfd | HUB | Device found on port 6 of hub "".
I: [21:18:44] USB Fkt Init | Init Fkt | Fkt 0x5FE09790 initialized
I: [21:18:44] hub.usbfd | HUB | Hub "Dell Multimedia Pro Keyboard Hu" has TT thinktime of 8 full speed bittimes and protocol 0
I: [21:18:45] hub.usbfd | Hub port | Device at port 6 of hub "" is high-speed.
E: [21:18:45] USB stack | New Fkt | fkt: 0x5FE098D0 = Level 2
I: [21:18:45] hub.usbfd | HUB | Device on hub port 6 successfully added.
I: [21:18:45] USB Fkt Init | Init Fkt | Fkt 0x5FE098D0 is {Vendor: 0x058F, Product: 0x6362, Class: 00.00}
I: [21:18:45] hub.usbfd | HUB | Device found on port 7 of hub "".
I: [21:18:45] USB Fkt Init | Init Fkt | Fkt 0x5FE098D0 initialized
I: [21:18:45] hub.usbfd | HUB | Device found on port 1 of hub "Dell Multimedia Pro Keyboard Hu".
I: [21:18:45] MassStorage Device Task | Massstorage | Lun 0 has device type 0x00 (Direct access) and is removable
I: [21:18:45] MassStorage Device Task | Massstorage | Lun 1 has device type 0x00 (Direct access) and is removable
I: [21:18:45] MassStorage Device Task | Massstorage | Lun 2 has device type 0x00 (Direct access) and is removable
I: [21:18:45] MassStorage Device Task | Massstorage | Lun 3 has device type 0x00 (Direct access) and is removable
I: [21:18:45] hub.usbfd | Hub port | Device at port 7 of hub "" is high-speed.
E: [21:18:45] USB stack | New Fkt | fkt: 0x5FE09C90 = Level 2
I: [21:18:45] hub.usbfd | HUB | Device on hub port 7 successfully added.
I: [21:18:45] hub.usbfd | HUB | Driver Running
I: [21:18:45] USB Fkt Init | Init Fkt | Fkt 0x5FE09C90 is {Vendor: 0x0424, Product: 0x2240, Class: 00.00}
I: [21:18:45] USB Fkt Init | Init Fkt | Fkt 0x5FE09C90 initialized
I: [21:18:45] hub.usbfd | Hub port | Device at port 1 of hub "Dell Multimedia Pro Keyboard Hu" is low-speed.
E: [21:18:45] USB stack | New Fkt | fkt: 0x5FE09D30 = Level 3
I: [21:18:45] hub.usbfd | HUB | Device on hub port 1 successfully added.
I: [21:18:45] hub.usbfd | HUB | Driver Running
I: [21:18:45] USB Fkt Init | Init Fkt | Fkt 0x5FE09D30 is {Vendor: 0x413C, Product: 0x2011, Class: 00.00}
I: [21:18:45] USB Fkt Init | Init Fkt | Fkt 0x5FE09D30 initialized
I: [21:18:46] MassStorage Device Task | Massstorage | Lun 0 has device type 0x00 (Direct access) and is removable
I: [21:18:47] MassStorage Device Task | Sys_EndInitialAttachmentPhase | Initial USB Attachment Phase terminated
I: [21:18:54] USB stack Process | | USB System Software Process started.
I: [21:18:54] USB stack Process | | Reading FD descriptors...
I: [21:18:54] USB stack Process | | ...FD infos read
I: [21:18:54] USB stack Process | | Starting HCDs...
I: [21:18:54] USB stack Process | | ...HCDs started.
I: [21:18:54] USB stack Process | | USB stack fullbooted
I: [21:18:54] USB FD ifc start | Sys_EndInitialAttachmentPhase | Initial USB Attachment Phase terminated
I: [21:19:00] hub.usbfd | HUB | Detaching Function removed from hub port 1
I: [21:19:01] hub.usbfd | HUB | Device found on port 1 of hub "".
I: [21:19:01] hub.usbfd | Hub port | Device at port 1 of hub "" is low-speed.
E: [21:19:01] USB stack | New Fkt | fkt: 0x51921df0 = Level 2
I: [21:19:01] hub.usbfd | HUB | Device on hub port 1 successfully added.
I: [21:19:01] USB Fkt Init | Init Fkt | Fkt 0x51921DF0 is {Vendor: 0x1C4F, Product: 0x0003, Class: 00.00}
I: [21:19:01] USB Fkt Init | Init Fkt | Fkt 0x51921DF0 initialized
E: [21:19:01] hid.usbfd | HID driver | Setup error: Error reading HID Report Descriptor (-33)

I: [21:19:01] hid.usbfd | HID driver | Failed to load ReportDescriptor
E: [21:19:01] hid.usbfd | HID driver | Interface binding failed. Error -33
I: [21:19:01] hub.usbfd | HUB | Detaching Function removed from hub port 1
I: [21:19:02] hub.usbfd | HUB | Device found on port 1 of hub "".
I: [21:19:02] hub.usbfd | Hub port | Device at port 1 of hub "" is low-speed.
E: [21:19:02] USB stack | New Fkt | fkt: 0x51921e90 = Level 2
I: [21:19:02] hub.usbfd | HUB | Device on hub port 1 successfully added.
I: [21:19:02] USB Fkt Init | Init Fkt | Fkt 0x51921E90 is {Vendor: 0x1C4F, Product: 0x0003, Class: 00.00}
I: [21:19:02] USB Fkt Init | Init Fkt | Fkt 0x51921E90 initialized
E: [21:19:09] hid.usbfd | HID driver | Setup error: Error reading HID Report Descriptor (-33)

I: [21:19:09] hid.usbfd | HID driver | Failed to load ReportDescriptor
E: [21:19:09] hid.usbfd | HID driver | Interface binding failed. Error -33
I: [21:19:09] hub.usbfd | HUB | Detaching Function removed from hub port 1
I: [21:19:10] hub.usbfd | HUB | Device found on port 1 of hub "".
I: [21:19:10] hub.usbfd | Hub port | Device at port 1 of hub "" is low-speed.
E: [21:19:10] USB stack | New Fkt | fkt: 0x51921df0 = Level 2
I: [21:19:10] hub.usbfd | HUB | Device on hub port 1 successfully added.
I: [21:19:10] USB Fkt Init | Init Fkt | Fkt 0x51921DF0 is {Vendor: 0x1C4F, Product: 0x0003, Class: 00.00}
I: [21:19:10] USB Fkt Init | Init Fkt | Fkt 0x51921DF0 initialized
E: [21:19:17] hid.usbfd | HID driver | Setup error: Error reading HID Report Descriptor (-33)

I: [21:19:17] hid.usbfd | HID driver | Failed to load ReportDescriptor
E: [21:19:17] hid.usbfd | HID driver | Interface binding failed. Error -33
I: [21:19:17] hub.usbfd | HUB | Detaching Function removed from hub port 1
I: [21:19:18] hub.usbfd | HUB | Device found on port 1 of hub "".
I: [21:19:18] hub.usbfd | Hub port | Device at port 1 of hub "" is low-speed.
E: [21:19:18] USB stack | New Fkt | fkt: 0x51921e90 = Level 2
I: [21:19:18] hub.usbfd | HUB | Device on hub port 1 successfully added.
I: [21:19:18] USB Fkt Init | Init Fkt | Fkt 0x51921E90 is {Vendor: 0x1C4F, Product: 0x0003, Class: 00.00}
I: [21:19:18] USB Fkt Init | Init Fkt | Fkt 0x51921E90 initialized
E: [21:19:25] hid.usbfd | HID driver | Setup error: Error reading HID Report Descriptor (-33)

I: [21:19:25] hid.usbfd | HID driver | Failed to load ReportDescriptor
E: [21:19:25] hid.usbfd | HID driver | Interface binding failed. Error -33
I: [21:19:25] hub.usbfd | HUB | Detaching Function removed from hub port 1
I: [21:19:26] hub.usbfd | HUB | Device found on port 1 of hub "".
I: [21:19:26] hub.usbfd | Hub port | Device at port 1 of hub "" is low-speed.
E: [21:19:26] USB stack | New Fkt | fkt: 0x51921df0 = Level 2
I: [21:19:26] hub.usbfd | HUB | Device on hub port 1 successfully added.
I: [21:19:26] USB Fkt Init | Init Fkt | Fkt 0x51921DF0 is {Vendor: 0x1C4F, Product: 0x0003, Class: 00.00}
I: [21:19:26] USB Fkt Init | Init Fkt | Fkt 0x51921DF0 initialized
W: [21:19:33] USB FD fkt start | USBFktGetCfgDescriptors | Error reading config dsc from Fkt 0x51921DF0
E: [21:19:33] USB FD fkt start | USBFktGetCfgDescriptors | Failed to read config from Fkt 0x51921df0 - error -36
E: [21:19:33] USB FD fkt start | FD launcher | Failed to read CfgDsc
I: [21:19:49] hub.usbfd | HUB | Detaching Function removed from hub port 1
I: [21:19:50] hub.usbfd | HUB | Device found on port 1 of hub "".
I: [21:19:50] hub.usbfd | Hub port | Device at port 1 of hub "" is low-speed.
E: [21:19:50] USB stack | New Fkt | fkt: 0x51921df0 = Level 2
I: [21:19:50] hub.usbfd | HUB | Device on hub port 1 successfully added.
I: [21:19:50] USB Fkt Init | Init Fkt | Fkt 0x51921DF0 is {Vendor: 0x1C4F, Product: 0x0003, Class: 00.00}
I: [21:19:50] USB Fkt Init | Init Fkt | Fkt 0x51921DF0 initialized
--------------------------------------------------------
Today I buy Dell 6 button USB laser mouse. This is best mouse for my sam. Not only work in any USB port with no cutted kicklayout but also is not very high priced!!! Dell is popular in many countries so I recomended this mouse for all !!!
Still got "interface binding failed - error 11" on last position USB log and sometimes error 33, but there are no visible negative effect of this errors.
Mouse problem is solved :)
hardware: sam460ex, Scythe KAMA 2 Card Reader, Sil 3114, Radeon HD 4650
interest: ami-lineapolis developer
mrdarek
 
Posts: 12
Joined: Tue Aug 30, 2011 5:44 pm

Re: Update 3 scroll wheel no longer working

Postby Redlion » Fri Sep 02, 2011 1:20 am

Hi,

Sam460 Lite


I updated to Update 3 from an almost clean update 2, I have tried all the fixes that have been sugested but still can not get scroll to work.

If I edit out bootmouse and or bootkeyboard nothing works at all. If I add in the Hid.usbfd nonouse or keyboard.

On a normal setup sometimes the mouse does not work at all, I have had a quick look at the USB log there are a lot of fails errors 11, 15 and 33.

I have also lost sound. No amount of soft boots or restarts get mwe sound.


Redlion.
Redlion
 
Posts: 1
Joined: Thu Sep 01, 2011 12:31 pm

Re: Update 3 scroll wheel no longer working

Postby mrdarek » Fri Sep 02, 2011 7:53 am

For sam460 are not good solutions - only two: disabling USB2 (marking ehci) or buying new keyboard and mouse. For mouse I really recommended my Dell 6 button laser usb mouse - no high price. I also changed keyboard - now I have Dell multimedia keyboard with characteristic silver plate with scroll, but I not recomended it because is high price and multimedia extra buttons not work for Amiga (I was in desperation so I must buy it :D )
Wrong keyboard and mouse much lowering probability sound initialization...
hardware: sam460ex, Scythe KAMA 2 Card Reader, Sil 3114, Radeon HD 4650
interest: ami-lineapolis developer
mrdarek
 
Posts: 12
Joined: Tue Aug 30, 2011 5:44 pm

Re: Update 3 scroll wheel no longer working

Postby ssolie » Fri Sep 02, 2011 5:08 pm

mrdarek wrote:For sam460 are not good solutions - only two: disabling USB2 (marking ehci) or buying new keyboard and mouse.

Did you try the workaround?

Did you try powering down the machine, waiting +5 seconds and powering it back up again? Does the mouse work properly then?
AmigaOS Development Team Lead
Be authentic. Get AmigaOS.
User avatar
ssolie
AmigaOS Core Developer
AmigaOS Core Developer
 
Posts: 1000
Joined: Mon Dec 20, 2010 9:51 pm
Location: Canada

Re: Update 3 scroll wheel no longer working

Postby ChrisH » Fri Sep 02, 2011 8:25 pm

I don't have exactly the same problem, but I believe the cause is the same:

After my Sam440 finishes booting OS4.1u3, my KVM's mouse & keyboard simply don't work (or I only get Y-axis movement of mouse). I had similar (or possibly not so bad) problems with all earlier versions of OS4.1 too. The only way I solved it was by disabling bootmouse & bootkeyboard in Kicklayout. So given this part of the original Kicklayout:
MODULE Kickstart/hub.usbfd
MODULE Kickstart/bootmouse.usbfd
MODULE Kickstart/bootkeyboard.usbfd
MODULE Kickstart/massstorage.usbfd
MODULE Kickstart/uhci.usbhcd
MODULE Kickstart/ohci.usbhcd
MODULE Kickstart/ehci.usbhcd

I modified it to look like this:
MODULE Kickstart/hub.usbfd
;MODULE Kickstart/bootmouse.usbfd
;MODULE Kickstart/bootkeyboard.usbfd
MODULE Kickstart/massstorage.usbfd
MODULE Kickstart/uhci.usbhcd
MODULE Kickstart/ohci.usbhcd
MODULE Kickstart/ehci.usbhcd
;added hid to replace boot#?
MODULE Kickstart/hid.usbfd


Note that the new "hid" line has to be after some of the usb (uhci/etc) stuff or it doesn't work at all.


From the sound of it, the logic used to disable boot mouse/keyboard needs to be completely rewritten from scratch.

EDIT: I had it pointed out to me that my instructions were incomplete. I forgot to say:
Delete SYS:Kickstart/bootkeyboard.usbfd and bootmouse.usbfd.
Delete DEVS:USB/fdclasses/bootkeyboard.fdclass and bootmouse.usbfd.
Move hid.usbfd from DEVS:USB/fd/ to SYS:Kickstart/

ZeroG first explained the solution, but how you modify the Kicklayout file should follow my instructions since his is now slightly out-of-date for Update 3.

Also note that I found my (ITX) Sam440's bottom rear USB port to be a bit flakey, and so I plug my KVM into the top port.

EDIT: I discovered that I did not correctly install Update 3, due to me forgetting how the above changes were done, so I think it would be safer to make these changes INSTEAD:

Given this part of the original Kicklayout:
MODULE Kickstart/hub.usbfd
MODULE Kickstart/bootmouse.usbfd
MODULE Kickstart/bootkeyboard.usbfd
MODULE Kickstart/massstorage.usbfd
MODULE Kickstart/uhci.usbhcd
MODULE Kickstart/ohci.usbhcd
MODULE Kickstart/ehci.usbhcd

I modified it to look like this:
MODULE Kickstart/hub.usbfd
;MODULE Kickstart/bootmouse.usbfd
;MODULE Kickstart/bootkeyboard.usbfd
MODULE Kickstart/massstorage.usbfd
MODULE Kickstart/uhci.usbhcd
MODULE Kickstart/ohci.usbhcd
MODULE Kickstart/ehci.usbhcd
;added hid to replace boot#?
MODULE Devs/USB/fd/hid.usbfd


Note that the new "hid" line has to be after some of the usb (uhci/etc) stuff or it doesn't work at all.

You probably also need to:
Delete DEVS:USB/fdclasses/bootkeyboard.fdclass and bootmouse.fdclass
Last edited by ChrisH on Thu Sep 15, 2011 10:00 am, edited 5 times in total.
User avatar
ChrisH
Beta Tester
Beta Tester
 
Posts: 914
Joined: Mon Dec 20, 2010 10:09 pm

Re: Update 3 scroll wheel no longer working

Postby mrdarek » Fri Sep 02, 2011 8:32 pm

Wrong mouse always will be wrong (in update3!). After power down mouse sometimes initializing fast, sometimes very long time, sometimes it initializes even with active scroll!!! - just it totally random. Buying better, compatibile mouse is much better solutions - some mouses always work like dell mouse - no difference between update 2 and 3 for dell mouse.
.....I modified it to look like this.....

I test it but often got message window like "not found bootmouse driver", also not solving speed detection issue - OS try plugin new USB device and pop-up message, sometimes several times, with good mouse- device is plugged instantly and I not see this message.
Last edited by mrdarek on Fri Sep 02, 2011 8:40 pm, edited 1 time in total.
hardware: sam460ex, Scythe KAMA 2 Card Reader, Sil 3114, Radeon HD 4650
interest: ami-lineapolis developer
mrdarek
 
Posts: 12
Joined: Tue Aug 30, 2011 5:44 pm

Re: Update 3 scroll wheel no longer working

Postby ssolie » Fri Sep 02, 2011 8:40 pm

mrdarek wrote:Wrong mouse always will be wrong (in update3!). After power down mouse sometimes initializing fast, sometimes very long time, sometimes it initializes even with active scroll!!! - just it totally random. Buying better, compatibile mouse is much better solutions - some mouses always work like dell mouse - no difference between update 2 and 3 for dell mouse.

Don't toss the troublesome mice just yet. We will need them for testing.

When sba returns from his holiday he can look into the logs and try and figure out why some mice are being a bother.
AmigaOS Development Team Lead
Be authentic. Get AmigaOS.
User avatar
ssolie
AmigaOS Core Developer
AmigaOS Core Developer
 
Posts: 1000
Joined: Mon Dec 20, 2010 9:51 pm
Location: Canada

Re: Update 3 scroll wheel no longer working

Postby mrdarek » Fri Sep 02, 2011 8:48 pm

well, I live in Poland and not have much money for sending mouse to Hyperion for testing. I suggest buing esperanza mouse EM-102 for test - it low end device and cheap. Google image give picture this mouse on string "ESPERANZA EM102K" - but I not have "K" letter - but mouse looking similar
hardware: sam460ex, Scythe KAMA 2 Card Reader, Sil 3114, Radeon HD 4650
interest: ami-lineapolis developer
mrdarek
 
Posts: 12
Joined: Tue Aug 30, 2011 5:44 pm

Re: Update 3 scroll wheel no longer working

Postby ssolie » Fri Sep 02, 2011 8:57 pm

mrdarek wrote:well, I live in Poland and not have much money for sending mouse to Hyperion for testing. I suggest buing esperanza mouse EM-102 for test - it low end device and cheap. Google image give picture this mouse on string "ESPERANZA EM102K" - but I not have "K" letter - but mouse looking similar

I was thinking the other way around. Software is tad cheaper to send around. ;)
AmigaOS Development Team Lead
Be authentic. Get AmigaOS.
User avatar
ssolie
AmigaOS Core Developer
AmigaOS Core Developer
 
Posts: 1000
Joined: Mon Dec 20, 2010 9:51 pm
Location: Canada

Re: Update 3 scroll wheel no longer working

Postby yoodoo2 » Sat Sep 03, 2011 4:46 pm

Just for info really:

I've been using a wireless Keysonic keyboard/trackpad combo on a Samm440-ep under update 2 with no problems. When booting update 3, LoadMonDrvs failed to, well, load and I was left with just the FakeNative and Producitivity modes and a low res, low colour Workbench.

After a fair bit of experimentation (as I started by looking for a Monitor/Graphics problem), the end result was that update 3 USB modules don't like the KeySonic device, well, not during boot-up anyway. If I boot with a different keyboard/mouse, I can then swap to the Keysonic which continues to work fine under normal operation. The KickstartLayout changes listed above by ChrisH also allow the KeySonic to work fine.

Not sure why the USB system should block LoadMonDrvs, or why it seems to only have happened to me; presumably the startup sequence is blocked while waiting for the KeySonic to respond/activitate somehow.
yoodoo2
 
Posts: 9
Joined: Wed Aug 31, 2011 10:07 am

PreviousNext

Return to General AmigaOS

Who is online

Users browsing this forum: No registered users and 9 guests