Recent Posts

Pages: [1] 2 3 ... 10
Hardware / Using a Corsair K70 Keyboard on a KVM under ArcaOS
« Last post by Mark Szkolnicki on Today at 11:34:20 pm »
Hi All!

Its been quite a few months (21 in fact) since I had any time to stop in to the OS2world forums, to participate, as between pandemic and forest fire response its been a busy time. Hope everyone remains well in what has become a rather extraordinary time in history.

Just thought I'd drop off a tip I learned today, related to getting a Corsair K70 keyboard on a Belkin KVM working with ArcaOS.

As background, I had worn out my keyboard late last year after years of typing, and was in the market for a new one - I wanted it for both use in a professional manner (purely for typing) and for gaming (in the odd time I have for such).

As a result I came across the Corsair K70 Mk. 2, which had very high marks - it is a very well made (aluminum frame) keyboard with a rugged Gold Contact Cherry MX mechanical movement. I've always preferred mechanical keyboards to membrane, but as with all things it runs to personal preference.

It also is an extremely attractive bright back lighted keyboard, in multiple colours in a variety of patterns, which looks good whether in daylight or at night.

Purchasing the keyboard last December I attempted to hook it up to first one computer directly, and then through my KVM switches, to my ArcaOS set-ups, only to be disappointed with the fact that the keyboard did not to seem to be recognized by either the KVMs or the system, under ArcaOS, although it functioned correctly in the Windows set-up (Windows 7 Pro) when directly connected on the computer I was using for test purposes.

I had little time to troubleshoot the problem, so I was forced to use another keyboard I then purchased for use with my KVM switchs, which worked, but was certainly not the same in either style nor quality.

Returning to the problem two days ago, I finally found a solution on a couple of forums where people had reported the same problems with Corsair keyboards and KVM switches, and a link to a blog by a Simon Fredsted:


It seems that Simon found that some Corsair keyboards won't work in some computer's BIOS due to gaming optimizations -- any keys you press before booting an OS will not be recognized. The same is true for access through KVM switches.

The K70 has an option which is called "BIOS mode" which may be enabled by pressing the "WinLock" key (on the K70 this is located at the top left of the keyboard as a specialty key with a Lock symbol on it) for five seconds, when the keyboard is powered, and then holding down the F1 key (so both keys are pressed) for an additional 5 seconds.

After that release the WINLOCK key - the keyboard LED's go off then back on, and the Scroll Lock LED on the keyboard should blink continuously. After a second, release the F1 key.

Using that procedure the K70 keyboard is now recognized when I boot up ArcaOS, including the colour keyboard display which I had enabled.

From Simons blog, using BIOS mode limits some of the gaming optimizations inherent to the keyboard. To turn off BIOS mode when using them under Windows, he indicates that you simply perform the procedure again - the blinking Scroll Lock LED should turn off.

I've tested exiting and re enabling BIOS mode, as well as turning the KVM off and then on (the K70 seems to retain BIOS mode until it is disabled as above, possibly because of the keyboard onboard memory)

I have not as yet tried using the keyboard directly connected to one computer, or using it for gaming purposes under windows, but thought this tip might be useful for others here who were using this model or others in the Corsair line and trying to access ArcaOS.

Best to all and a fine day to you!

Utilities / Re: MeShell commandline frontend timetable
« Last post by Dariusz Piatkowski on Today at 10:20:04 pm »

I just recently looked into this shell overlay you developed, very promising!

There are a couple of issues I'm running into, but before I report on those I am trying to troubleshoot further (this is the START of the application, and how the VIO window is auto-recognized thus causing the started task to pop to the foreground - I have numerous utils for which this simply does not happen at all, and attempting to manipulate the various config options simply leave the background VIO window in a hung state).

Anyways, in the meantime, question re: Copy/Paste functionality. It would appear that your MeShell disables this in the normal CMD windows, is that correct?

Specifically, I use the simplified Copy/Paste implmented by Xit utility (which is bound to the LEFT and RIGHT mouse buttons). MeShell has Xit disabled (as that was causing problems with your app - it would not start), however for reasons I cannot tell, my regular CLI sessions no longer have the Xit provided Copy/Paste functionality.

That's kind of a "deal-breaker" that what you really intended to do?

Setup & Installation / Re: YUM default platform setting
« Last post by Martin Vieregg on Today at 09:45:36 pm »
I have tried now the SMT setting in the BIOS (advanced - CPU). ArcaOS has got still the four pulse graphs. So it seems that SMT and Hyperthreading is the same indeed.
Storage / Re: exFat or FAT32 ?
« Last post by Martin Vieregg on Today at 09:17:45 pm »
I have got ArcaOS 5.0.2 and have installed a FAT32.IFS Netlabs driver (0.10-r384)
Setup & Installation / Re: YUM default platform setting
« Last post by Martin Vieregg on Today at 09:09:32 pm »
I only found a switch to turn off SMT. But if I understand right, this is not the same. Symmetric Multi Threading means several cores are used for one thread each, and Hyperthreading means two threads are running on the same core. Is that right? Of course I still want to use all my cores.
Setup & Installation / Re: YUM default platform setting
« Last post by ivan on Today at 07:40:36 pm »
I found the easiest way to turn off hyperthreading was to go into the UEFI bios and do it there. once done it stays done but can be very hard to find,
At least, "firefox-31.8.0.en-us.os2.beta_5-wpi.wpi" still works.
Setup & Installation / Re: YUM default platform setting
« Last post by Martin Vieregg on Today at 05:36:14 pm »
One of the upgrade steps changes your platform from i686 to pentium4.

But on the computer working fine which shows still "i686", I did make also the same (all) upgrade steps.
There's perhaps one week time difference. Can it happen that in this week, such minor changes were made on the server?

I can also try to copy the directories
Code: [Select]
usr/* var/* etc/* sys/*from the fine working installtion to the problem installation.
I hope that all information about the system drive is stored in environment variables, because the drive letters are different.
Comments, Suggestions & Questions / Re: Hobbes (Files) Reoganization
« Last post by Dave Yeo on Today at 04:31:32 pm »
Hi Martin, missed this.
For the name of the directory, either of your ideas seems fine.
As for which versions. I guess if you want to trim older ones, I'd keep at least the 38ESR and the 45ESR various versions as there still seems to be people who prefer SM 2.35 at least and they still work. Older versions are getting useless as they don't support new enough encryption.
Setup & Installation / Re: YUM default platform setting
« Last post by Dave Yeo on Today at 04:26:24 pm »
Hi Martin, you will have to turn off the hyperthreading on the command line of ACPI, not the simplest thing to do as yo have to figure out which cores are real and which are fake and use a bitmask to only use the real ones. First try adding /CPUMASK=1 to the PSD line in config.sys to test with only one CPU. If OO now works on the problem system, that will tell you it is a hyperthreading problem.
The PSD documentation is under x:\sys\docs\ACPI as psd_en.pdf. See the ACPI command line section. You might have to open an issue to get help.
As for the i686 vs Pentium 4 thing, Bitwise seems to be guiding us to Pentium 4 systems to support the new browser. As Neil said, more to come.
Pages: [1] 2 3 ... 10