Help, using Mac Bluetooth Keyboard on PC?


Recommended Posts

Maybe you should try to switch stack from Microsoft to Widcomm, or vice versa?

585919603[/snapback]

I started with old Widcomm's, was it 1.3xx as it worked with it as I described. I also tried with Xp SP2's stack and it worked the same.

I've tried with widcomm 1.4xx and 3xx and with both the keyb didn't work. The PIN-code sections was grayed out as many ahs described. Haven't tried the version 4 yet, because all those widcomm versions I have tried are provided by Logitech and I haven't gotten any of the cracked versions work. But I'll try the version 4...

Hope it helps.

please help!! i have been trying this for ages and am just about to return the keyboard. i have d-link 120 bluetooth in my pc but it uses the xp sp2 drivers as they knock out the d-link software. is this possible to link with the d-link dongle and the microsoft drivers if so please could someone post a step by step. would be much appreciated as i am at my wits end trying this. the bluetooth finds the keyboard recognises it but thats about it. i tried without a passkey. keyboard didn't work and the pairing ended. help!! :( :no:

hi

i had the same problem with the belkin bluetooth adapter, so i uninstalled the belkin software and let widows xp sp2 find the bluetooth dongle.then i asked it add devices, it found the keyboard so i tried not assignig a passkey but windows told me everything was fine but the keyboard didn't work. so i asked windows to give the keyboard a passkey, i then pressed enter and added the key, works fine now. and looks lovely set up as part of my media centre.

585844389[/snapback]

tried this without passkey. so adding a pass key made it work yeah??

could it be that simple

  • 4 weeks later...

Using a Micro$oft Bluetooth 2.0 adapter and an Apple wireless keyboard was effortless to get to work together. It seems that people must be having problems with M$ Bluetooth 1.? adapters or some other Bluetooth Adapter.

The only problem is that the "=" on the number pad does not work BUT this can be remapped by using Sharpkeys. There is no scroll lock, print screen or pause break key either and all but the pause/break key can be remapped (who needs a scroll lock key anyways?)

Unfortunately, the volume up/down, mute and eject buttons don't work and I cannot find a work around for these.

The "clear" button maps automatically as a number lock key (this can also be remapped by Sharpkeys as well)

Where did i get a 2.0 adapter? ... Ebay of course (the only one I've seen - must of been with a keyboard or mouse combo unit from M$ that the seller didn't want or need).

The personal area network with Bluetooth Network Connection also automatically configured. (M$ must of worked the bugs out ... now they just need to sell the bluetooth usb item by itself).

  • 1 month later...

Boy was this a pain in the neck to figure out... and the solution isn't 100% pretty,

but it sure works well! I've come to the conclusion that the MX900's BT hub is not

that great... and D-Link's DBT-120 USB hub is wonderful! The 3.x WIDCOMM drivers

just don't like the Apple Wireless Keyboard in that it won't pair correctly since

the pairing key is never displayed (as mentioned by previous poster). Funny enough

the 1.x WIDCOMM drivers do infact work.... BUT the Apple Wireless keyboard

fails to connect at login time leaving you without a way to enter a password in

during login if you use the MX900 + WIDCOMM solution. SO in the end here is what

I used :

NO WIDCOMM drivers. I installed Logitech's Setpoint 2.2, but then unistalled WIDCOMM.

Use the DBT-120. That little sucker rocks!

Use Microsoft's Bluetooth stack... ugly windows but works great!

Only plug the MX900 base into the AC adapter and not into the computer...

(this disables the MX900's BT hub, but allows it to recharge the mouse batteries).

The MX900 mouse + Apple's Wireless Keyboard works 100% now.

If you have any questions please feel free to ask!!!

:yes:

I've got an old Epox dongle that's spare since I upgraded my mac's dongle to a DBT-120 (for headset support).

Out of curiosity, I plugged it in.

Windows picked it up and installed its own drivers, and it's ready to go. I disable BT on my mac and turn the keyboard off, then go to add device on the PC. Turn the keyboard on, click search, click add, type in a pairing code, hit next, type in in on the keyboard. Bang, one working apple bluetooth keyboard.

Just to make sure, I rebooted. About 5 seconds after i'm presented the desktop, the keyboard's working.

Typing this with it now :)

  • 3 months later...

Thank God I found this post.

I was close to my harakiri. ;)

I'm having exactly the same problem (the PIN that doesn't show up to be typed).

I'm using in my notebook (Acer Aspire 2012WLMi) an internal BT module from Actiontec (BTM-200). My OS is WinXP SP2. The installed driver is HP 3.0.1.905 (great, except by this little mess); the driver supports HID (human interface device).

I already tried 3.0.1.914 and 4.0.1.2101, both patched (that license file issue)

Keyboard is OK, since I've tested:

1. in several Macs. Flawless. Mac OS generates a PIN (yes, this one is showed on screen) and you just type in the KB.

2. in a desktop PC, with the Microsoft built-in driver (SP2). Same thing as Mac: you choose a PIN, type in KB and everything is working.

3. in a desktop PC, with some other driver versions from Widcomm. Sometimes, driver don't find the KB. Sometimes, finds and allows choosing a PIN (but after typing, you get an error).

In cases [2] e [3] I've tested in a desktop PC with a Olympia Bluetooth dongle (CSR-like). I'm trying to update my Actiontec internal module to use Microsoft's built-in (and very limited) driver, but I can't even choose it from the "Update driver" list. I uninstalled the most recent driver version, but the "Generic Bluetooth Radio" doesn't show up.

Any help would be really appreciated. Thanks in advance.

  • 4 months later...

Hello.

I bought an Apple Wireless Keybaord and a D-Link DBT-120 USB bluetooth dongle to try to use the keyboard with Windows XP. I installed the drivers that came with the

The keyboard is not being recognized.

Can anyone guide me through the proper steps to get the keyboard working?

Thanks,

Avi

Actually, I tried the procedure quoted below, and the Bluetooth Device Manager finds the keyboard, and I get the Add Bluetooth Device Wizard "Windows is Installing Your Device." Then I click finish. But the keyboard doesn't work, and when I close and reopen the Bluetooth Devices control panels, the keyboard does not show up.

Any thoughts??

Thanks,

Avi

I've got an old Epox dongle that's spare since I upgraded my mac's dongle to a DBT-120 (for headset support).

Out of curiosity, I plugged it in.

Windows picked it up and installed its own drivers, and it's ready to go. I disable BT on my mac and turn the keyboard off, then go to add device on the PC. Turn the keyboard on, click search, click add, type in a pairing code, hit next, type in in on the keyboard. Bang, one working apple bluetooth keyboard.

Just to make sure, I rebooted. About 5 seconds after i'm presented the desktop, the keyboard's working.

Typing this with it now :)

  • 1 month later...

Could someone please comment as to whether the "caps lock" led works when using with a PC? (I read somewhere that the Apple Bluetooth does have an onboard caps lock LED...can't say, I've not seen one but I want to buy one because of the small footprint).

Any other comments, specifically....

the keyboard feel

what sucks? (eg I've seen some comments that the keys are too close together etc)

are drops frequent?

Also is the general consensu to go with the D-Link bluetooth adapter?

Many thanks in anticipation.

Hank McSpank

[Yank it, crank it & then rip the knob off]

Im using bluetooth with XP but seem to be having trouble with the Apple BT wireless keyboard pairing.

Im using the D-Link 120 dongle.

Everytime I restart windows i need to pair it again or else it won't work. The keyboard also needs to be switched on and off before re pairing.

Windows recognizes the keyboard after booting but it won't establish two way communication to be able to type. It shows the icon of a checkmark instead of the usual two green arrows and two way comm in widcomm.

It works flawlessly if I dont restart.

Any ideas how to make it work????

Hi!

I've succeeded in getting the Apple Wireless Keyboard to work on XP. Thanx to gunpowda and other helpful posts!

I thought I'd share some tips... It wasn't easy... :rolleyes:

I've been using the wireless keyboard for a couple of days and it works extremely well. Here's what ya get:

  1. Keyboard auto-pairs invisibly before XP login. It just works. No futzing after each restart (that would have been a deal-killer)
  2. Caps lock light works correctly. All keys work, except the 4 multimedia keys top right. Haven't looked into that yet.
  3. In BIOS screens and other very early startup events, the bluetooth of course isn't running yet... :)
  4. So smooth. Nice and fast to type on. Quiet action. No interference or stickyness despite all the other wireless gear I've got running.

This is NOT a definitive how-to, but might inspire...

I'm using a fairly new Bluetooth USB adapter: "Trust Bluetooth 2.0 EDR USB Adapter, BT-2200Tp"

All the new Widcomm/Broadcom bluetooth stacks (versions 4.1+ and 5.0+) hit you with the grayed out pairing box Gunpowda posted about. It's a brick wall, don't bother trying to get around it.

You need an old Widcomm driver. Version 1.4 did the trick for me, but 1.3 and earlier may work.

1.4 finds the keyboard and prompts you with multiple choices for pairing: autopairing, choose PIN, et c.

Get to that screen and you're golden.

Driver repository: The GSM-HOSTING forum is great for pointers to very old (and v. recent) drivers.

http://forum.gsmhosting.com/vbb/showthread.php?t=106274

All the best -R.

Thanks everyone for your effort. I'm replying this post using apple wireless keyboard.

I'm glad i saw this post and do the right thing beofore i stepped out to buy BT adapter.

I'm using windows xp sp2 and DBT-120 adapter. The main issue i encounter is still replacing the MS BT driver with the widcomm driver come with DBT-120.

I found a good cocument teaching you how to:

http://www.e-beam.com/support/Switching_fr..._to_WIDCOMM.pdf

However, I have to do the switching driver thing in "safe mode" . Otherwise, the widcomm driver won't show up in the stack when i update the MS BT driver.

Now, everything works very good. :D

everyone ....strange things happened here.

MS BT generic driver seems working better than widcomm~~ :o

The thing is that i found the keyboard sometimes worked but sometimes didn't when i restarted the computer. I have to mannually disconnect and connect again.

Therefore i decided to uninstall widcomm driver and restart and then reinstall again and see if it can automatically get connected every time i restart.

And then of course the windows generic driver took place aftr i uninstall widcomm and restart the computer.

Then i suddenly had the idea that why don't i just give the generic driver a try before i reinstall widcomm driver and replace MS BT driver.

To my surprise, it works. Now i felt stupid that i spent lots of time yesterday just trying to figure out how to replace it with widcomm. :D

Hello all.

I am using my Apple Keyboard with the new drivers without having to revert to the old drivers.

Its very easy. It took me a while to figure out how, but here is how.

With the regedit modify these two values.

HKEY_CURRENT_USER\Software\Widcomm\BtConfig\General

Set

PinCodeWord

To a value of

1111

Set

UseFixedPin

To a value of

1

Then attempt pairing.

Whne you get to the greyed PIN screen on the Apple Keyboard type

1111

Then Press the Return key on the Apple keyboard

Voila paired.

I have attempted to try other ways subsequentl, but I could never figure out how to UNPAIR the keyboard.

BeDammit

Ok, my UK Mac bluetooth keyboard seems to work just fine with my microsoft bluetooth dongle on XP - nothing special to do ....it just worked.

BUT I have a simple key mapping problem that's driving me potty. ....

by using a british keyboard listed under regional & language input languages, I can either have my ? key mapped to it's correct key (ie above the number 3) BUT unfortunately the @ and " symbols are swapped

OR

by using a US keyboard listed under regional & language input languages, I can have the @ and " symbols on their correct keys BUT then I get a # instead of a pound sign!!

I can't seem to work out a way to get the ?, @ and " symbols on their correct keys! (& even if I did, where would the hash key be?!)

Edited by HankMcSpank
  • 1 month later...

Hello all.

I would like to thanks BeDammit for his brilliant solution.

I' ll add some extra information to help people flawless set up their Apple Bluetooth keyboard on Windows XP.

1. Press Win Start button, choose Run and then type regedit and press enter to access windows registry editor.

2. Into the registry editor search for and select -> HKEY_CURRENT_USER\Software\Widcomm\BtConfig\General

3. Set the key 'PinCodeWord' to a decimal value of 1111

4. Set the key 'UseFixedPin' to a decimal value of 1

5. Then attempt pairing. When you get to the greyed PIN screen type 1111 using OTHER keyboard THAN Apple Bluetooth keyboard.

6. Press the Return key on the Apple keyboard.

7. Enjoy your nice Keyboard.

I think this one is the best solution cause you don't have to mess with windcomm driver version.

Thanks again BeDammit.

Edited by dongaspa
  • 2 weeks later...

Hello to all,

Yeepee I also manged to get my Apple wireless Keyboard to work on my PC very well (4hours non-stop thought).

For info I have a BlueTooth USB Dongle running WIDCOMM drivers ver 1.4.2.8

I would just like to add some more info in there :

- 1

Keyboard is OK, since I've tested:

1. in several Macs. Flawless. Mac OS generates a PIN (yes, this one is showed on screen) and you just type in the KB.

2. in a desktop PC, with the Microsoft built-in driver (SP2). Same thing as Mac: you choose a PIN, type in KB and everything is working.

3. in a desktop PC, with some other driver versions from Widcomm. Sometimes, driver don't find the KB. Sometimes, finds and allows choosing a PIN (but after typing, you get an error).

- First of all I've never did install a BlueTooth device before that so I would like to add an important step there.

About point n?2 : you have to use 2 Keyboards, for sure you need your Apple Wireless Keyboard(AWKB) + another one that is working well to type in the PIN when pairing.

About point n?3 : I had exactly this problem but there is a solution after a reboot only when you choose to add a new Bluetooth device, just before clicking on detect, turn on your AWKB, it should be detected properly else go back then turn off your AWKB then try again until it detects your AWKB.

As soon as it is detected do not wait for the search for new devices to end : select the Apple keyboard in the list of detected devices then hit next as speed as possible.

You're now on the screen where you have to pair your AWKB to the computer, you have to be quick (i tried many timings believe me) remove the random number and enter with your other keyboar1111 i>then right after clicking on the button to start the pairing use your Apple Wireless KB to blind inpu1111 Enteri> it should detect it.

If you still have problems I noticed that it's better to input the digits from the numpad on the AWKB (because you have to hold shift to access other digits).

For some reason on some computers the Enter key either is the one from the numpad either it is the main Enter key.

2 - It's important to enter something different that 0000 if you have to login using ctrl+alt+suppr. because you won't be able to put that value in PinCodeWord. I also want to add that PinCodeWord is a Dword value you have to create.

3 - I found a very interesting program named autohotkey (http://www.autohotkey.com/) this one is a little jewel.

Scriptable remapping of all keyboards keys !! Woohoo

You can even have it to turn scripts to executables that mean you don't even have to install the soft to benefit of the remapping.

For now I remapped :

F13 to launch an app

F14 F15 F16 are Mute | Vol- | Vol+

I even phisically switch the F buttons with the Vol buttons so the illusion of controlling sound is perfect.

There's also a small OnScreenDisplay that pops up to show you the volume status each time you push Vol+ or Vol-. I told you thatthing was sweet !!!

= (numpad one) still nothing

Hope it helps,

Answer here if you want to test the my key mapping I'll put the exe online.

Edited by zerofil
  • 1 year later...
  • 3 weeks later...
  • 3 months later...
Hello all.

I would like to thanks BeDammit for his brilliant solution.

I' ll add some extra information to help people flawless set up their Apple Bluetooth keyboard on Windows XP.

1. Press Win Start button, choose Run and then type regedit and press enter to access windows registry editor.

2. Into the registry editor search for and select -> HKEY_CURRENT_USER\Software\Widcomm\BtConfig\General

3. Set the key 'PinCodeWord' to a decimal value of 1111

4. Set the key 'UseFixedPin' to a decimal value of 1

5. Then attempt pairing. When you get to the greyed PIN screen type 1111 using OTHER keyboard THAN Apple Bluetooth keyboard.

6. Press the Return key on the Apple keyboard.

7. Enjoy your nice Keyboard.

I think this one is the best solution cause you don't have to mess with windcomm driver version.

Thanks again BeDammit.

Thanks a lot dongaspa and BeDammit,

I tried for couple of hours to get the keyboard paired, I checked many internet forums until I got to this one.

I did exactly as in the instructions and voila! It works!

I'm extremely happy I got it working, I really love this keyboard for its size, design and functionality.

There is one more step which could be added to the instructions: after changing the registers' values I had to reboot

before successfully pairing the keyboard. But maybe this is common knowledge already :).

By the way, my configuration is Windows XP pro + SP2 and a Belkin BT dongle (driver version 5.0.1).

I should go now to sleep, its 1 a.m. but at least I solved the problem :).

thanks again,

AdiVio

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Disabling open on hover, great! That was so stupid! They need to do a fix, where if a network share is disconnected, it doesn't hang when opening "This PC" for 20 seconds.
    • Microsoft releases major feature updates for stock Windows 11 apps by Taras Buria In addition to releasing new Windows 11 preview builds, Microsoft announced that inbox Windows apps now have dedicated release notes in the official documentation. At long last, users have access to all the release notes for each app, with changes listed in chronological order. Microsoft used to announce feature updates for stock apps with each build. Now, with Windows Insider release notes hosted on the Microsoft Learn website, each app has a dedicated space for its changelog, which is very useful for those who want to track new features and improvements. Alongside that, Microsoft dropped massive feature updates for six stock apps: Clock, Media Player, Calculator, Voice Recorder, Photos, and Paint. Each app packs quite a lot of changes and new capabilities, so here are the release notes. Here are quick notes so that you can jump to the app you are interested in the most: Calculator Camera Clock Media Player Paint Photos Sound Recorder Here is what is new for the Calculator in version 11.2605.9.0: More accurate square-root results — Fixed rare cases where a calculation that should equal zero (like sqrt(2.25) - 1.5) returned a tiny leftover value instead. Readable text in High Contrast themes — Settings text now shows the correct colors in the High Contrast Aquatic and Desert themes. Fixed layout for right-to-left languages — For languages like Arabic and Hebrew, the graph, number pad, equation fields, and scroll buttons now appear correctly oriented. Reliable launch after upgrading — Fixed an issue where upgrading from much older versions could leave outdated settings that stopped the app from opening. Here is what is new for the Camera app (version 2026.2605.7.0): Zoom slider works on more cameras — The zoom slider now works on the latest cameras, respects your system zoom settings, and updates instantly when you change those settings. Full range of zoom levels — Fixed an issue where the zoom slider only showed three steps on some devices that zoom in finer increments. Front camera works on more devices — Resolved a problem that blocked the front-facing camera on certain wide-angle devices. More video resolution choices — You can now pick video resolutions that were previously hidden; the app shows a heads-up warning instead of removing them. QR links you can still use — When a scanned QR code points to something with no matching app, the link is now copied to your clipboard (with a notification) while still offering a Store search. Smarter default settings — When you haven't set a preference, the app now follows your system settings by default. The Clock app has a massive changelog with the following improvements in version 11.2605.9.0: Timers keep counting after they hit zero — When a timer runs out, it now keeps counting up (for example, -00:27:31) so you can see how far past the time you've gone. You can turn off the daily goal — Focus Sessions now include an "Off" option so you can skip setting a daily goal entirely. New 15-minute snooze option — Alarms now offer a 15-minute snooze interval. Run up to 3 countdowns at once — The Countdown Widget now supports three simultaneous countdowns, up from two. Timer Widget notifications now appear — Fixed an issue where the "timer finished" notification didn't show when the timer was started from the widget. Less clutter in Focus Sessions — Tasks you've already completed no longer show up in the Focus Session task list. More accurate focus progress — Fixed a rounding issue that could show your daily focus progress as a minute short (for example, 49 minutes instead of 50). Smoother World Clock comparisons — The World Clock compare page now loads dates as you scroll, so it feels more responsive. Up-to-date World Clock locations — Refreshed country and city names to match their current names. Correct sun and moon icons during midnight sun — Fixed an icon that wrongly showed a moon during all-day daylight in polar regions. Fixed back-button behavior in clock comparisons — Pressing back once now takes you back as expected, instead of jumping the date to 1926. Corrected the Newfoundland time zone — Newfoundland now uses the right time zone (St. John's). Disabled alarms stay looking disabled — Editing a turned-off alarm no longer makes it appear turned on. Cleaner timer cards — The expand button is now turned off on timer cards that have no time set, preventing actions that wouldn't do anything. Clearer theme setting — Updated the wording to "Choose your preferred app theme." Smoother Settings links — The "About" links in Settings no longer trigger an unexpected "switch apps" prompt. Fixed spacing in Spotify settings — Corrected uneven spacing in the Spotify settings card. Better focus visibility in High Contrast — The focus highlight in World Clock is now clearly visible in the High Contrast Aquatic and Desert themes. No more double announcements — Screen readers no longer read the timer value twice. Countdown names read correctly — Screen readers now properly announce the name of each countdown. Keyboard focus stays put — Focus no longer disappears after you press the Timer Reset button. Clearer alarm toggle for screen readers — Tidied up how the alarm on/off switch is announced. The Media Player app received plenty of changes as well (version 11.2605.14.0): Custom captions — You can now personalize how closed captions appear, with caption styling tied to your Windows caption settings, plus a quick link to open those settings directly. "Indexing" banner in the play queue — When your media library is still being scanned, a banner now explains why some items may not appear yet. Fixed the look of selected items — Corrected a layout glitch with selected items in lists. Fewer playback failures — Improved how the app recognizes supported file types, so more files play without issues. Playlists need a name — You can no longer accidentally save a playlist with a blank name. Cleaner look for empty playlists — Improved how a playlist appears when it has no items yet. More stable play queue edits — Fixed a crash that could happen when changing the play queue while the app was switching between sessions. Clearer "missing codec" message — Improved the dialog that appears when a file needs a codec you don't have, with clearer guidance on what to do. A big update is also available for Paint in version 11.2605.61.0: Adjustable eraser transparency — You can now control how transparent the eraser is. Cleaner stamp brush strokes — Fixed visible color shifts and artifacts when using stamp-style brushes. JPEG photos save in place — Opening a rotated JPEG and pressing Save now overwrites the original instead of unexpectedly prompting "Save As." No more crash on bad image files — Opening a damaged or invalid image, from within the app, by double click, or commandline, now shows a clear error message instead of closing the app. Classic selection behavior restored — The selection outline now hides while you move, resize, or rotate a selection, just like in classic Paint. Tidier AI image panel — Fixed missing spacing at the bottom of the AI image generation panel for a cleaner layout. Visible button hover in light theme — Toolbar split buttons now show a clear hover highlight in the light theme. Snappier toolbar — Streamlined how the ribbon lays out, giving a small speed boost at startup. Fewer background crashes — Fixed a crash that could happen while background tasks were finishing up. Stable app shutdown — Prevented rare crashes when closing the app. Fixed layer removal glitch — Deleting the active layer no longer leaves the layers list in an inconsistent state. Here is what is new in the Photos app (version 2026.11060.2004.0): AI watermarking — AI-generated or edited images can now carry a visible Copilot watermark. You choose Never, Always, or Ask Every Time in Settings, with a confirmation when saving. The watermarking is off by default in settings. Better viewing of small images and pixel art — Tiny images (like 16×16 pixel art) now zoom in far more to fill the screen and stay crisp instead of looking blurry. Select scanned text with the keyboard — When text is detected in an image, you can now navigate and select it using the arrow keys, Shift+Arrow, Home/End, and Ctrl+A, with a clear focus highlight. Fixed a crash in text recognition — Resolved a crash that could close Photos while detecting text in images; the app now recovers gracefully. Easier keyboard navigation — Tabbing through the navigation bar no longer stops on hidden controls, so it takes a single Tab to move past it instead of three. And finally, here is the Sound Recorder (version 11.2605.1.0): Waveform shows with Bluetooth mics — The live waveform now displays correctly when you record using a Bluetooth audio device. No more stray scrollbar — A non-working horizontal scrollbar no longer appears at the bottom of the waveform unless you've zoomed in. Mark button ready right away — The Mark button no longer looks grayed out until you hover over it after opening the app. Markers hidden for WAV files — Markers are now turned off for WAV recordings, since that format can't store them — so they're no longer lost silently. Smoother deleting — Quickly pressing Delete and Enter to remove several recordings in a row no longer triggers a "file doesn't exist" error. Fixed a memory issue — Resolved a memory leak that occurred each time a recording started. You can find all these changelogs in the official documentation here.
    • again, an article about Microsoft Edge and ridicules hater's comments
    • From this very same article: "For organizations that prefer a “more deliberate pace”, the Extended Stable channel remains an option."
    • Or every other browser, because they all behave the same, at least the mainstream ones. Firefox does exactly the same: background updates, restart to install them. Haters gotta hate, I guess.
  • Recent Achievements

    • Very Popular
      AndrewSteel earned a badge
      Very Popular
    • Veteran
      Taliseian went up a rank
      Veteran
    • One Month Later
      Clizby earned a badge
      One Month Later
    • One Month Later
      Timaximus earned a badge
      One Month Later
    • Week One Done
      Timaximus earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      499
    2. 2
      PsYcHoKiLLa
      170
    3. 3
      +Edouard
      162
    4. 4
      Steven P.
      85
    5. 5
      ATLien_0
      77
  • Tell a friend

    Love Neowin? Tell a friend!