If it helps any, the N50 has a device ID ending in 855 IIRC. You can go to the device properties in device manager to look at the Hardware Device IDs and find the two HID devices with matching IDs as an easier alternative to removing all your USB devices for those who can't use PS2 devices.
Pretty sure that there is no replacing of an "older" BCDedit file. The program states that they use the BCDedit.exe to make the changes. It does however makes a copy of the existing BCDedit file originally in the system, so you have a backup . I don't really see the harm in that. The way Vista Boot Pro was presented to me is that its simply a front end for BCDedit.exe. The exe can be a bit unwieldy with all the different switches.
Granted not all of us are computer savy. But I'm pretty sure I know what I'm installing as far as drivers. I usually do my homework before installing anything especially on something so new as Vista x64. The integrity check is a bit of nuisance for me. UAC, however, is always in effect. So again, not really a big deal as long as one does his/her homework before installing anything.
Unfortunately, most people that are trying to get this working have an N52, so I don't know if it's just meor if the N50 in particular won't work with this method.
Ok, I think we are talking about 2 different things. The method I listed and tested works for vista x64 on an n52. (that was what the OP was listing) You may be correct in that n50 drivers just don't exist for a n50 setup.
Fair enough, generally the N50 and N52 are interchangeable as they use the same drivers and software. I might need to go grab an N52 while I still can then.
Hi, just registered to reply to this thread - this has been a hot topic for me ever since moving to Vista64. At various stages I've had the XP 64bit beta driver working properly (but with driver signing turned off but that's a pain in the arse). Just recently I tried some of the other workarounds, but Vista decided to just use the generic HID compliant device driver and now I'm buggered till the signed driver comes out. It does work fine, but I've had to re-map all my games to the default generic Windows config, and of course there's no programming that thing (don't want to faff around with potentially problematic 3rd party software).
So in short, I'm glad I found this site for the insider news, and I can't wait to get my n52 back to full fighting power...
So in short, I'm glad I found this site for the insider news, and I can't wait to get my n52 back to full fighting power...
Glad to here it. Don't get me wrong aka1nas's method work's like a charm. The keyboard is recognized an HID compliant device (basically half a keyboard) and you can get all your buttons remapped in game to get the device working but you don't have much control over macros and such that really helps make the device shine. Some can live with it and some can't
Referring to your last statement, in my honest opinion, I doubt Belkin will release a set of signed drivers for vista much less x64 bit drivers for vista. I love my N52 and many others do as well, however I have yet to see any petition, spamming, forum polling, work in getting drivers out for this wonderful device. I count myself lucky that I fell upon the instructions to get it working (1st page). Its not as elegant a setup as I like it to be but it works.
PM if you need some help.
Referring to your last statement, in my honest opinion, I doubt Belkin will release a set of signed drivers for vista much less x64 bit drivers for vista. I love my N52 and many others do as well, however I have yet to see any petition, spamming, forum polling, work in getting drivers out for this wonderful device. I count myself lucky that I fell upon the instructions to get it working (1st page). Its not as elegant a setup as I like it to be but it works.
PM if you need some help.
And for anyone that does want macros and the like, take a look at AutoHotKey. I use it for custom desktop scripts, but I know there are many on the forums there using it for games.
It'll take time to code up what you want, but there's always the chance that someone else has done something similar that you can modify.
It'll take time to code up what you want, but there's always the chance that someone else has done something similar that you can modify.
Thanks for the Autohotkey link - I'll be checking out that for sure.
As for Belkin pulling their finger out, this message has been in their driver section for the last month or so:
Question
Will this device ever worked under Windows Vista 64 Bit?
Answer
We are currently reviewing the Vista 64 Bit driver. It should be posted soon on our website.
See here:
http://www.belkin.com/uk/suppo...C100&aid=7884&scid=293
And keep checking back here:
http://www.belkin.com/uk/suppo...C100&aid=6934&scid=293
Keeping my tiwtchy fingers crossed...
As for Belkin pulling their finger out, this message has been in their driver section for the last month or so:
Question
Will this device ever worked under Windows Vista 64 Bit?
Answer
We are currently reviewing the Vista 64 Bit driver. It should be posted soon on our website.
See here:
http://www.belkin.com/uk/suppo...C100&aid=7884&scid=293
And keep checking back here:
http://www.belkin.com/uk/suppo...C100&aid=6934&scid=293
Keeping my tiwtchy fingers crossed...
Originally posted by: aka1nas
Fair enough, generally the N50 and N52 are interchangeable as they use the same drivers and software. I might need to go grab an N52 while I still can then.
the n52 is seen as a gimped keyboard when plugged in- the n50 is just a directinput device. so an n52 will always work w/o software but an n50 might not.
i use the n50 (have an n52 also)
JD50
Lifer
- Sep 4, 2005
- 11,863
- 2,697
- 136
Just found this from a google search and it worked for me in vista 64...
"Here's how I got my Nostromo to work in Vista 64bit.
Download the v3g or x64 installtions for the Nostromo.
Open MSCONFIG and go to the TOOLS tab. Run down the list until you see "Disable UAC".
Go to the command line in Admin mode and type in either of these commands (depending on the version of Vista you have).
bcdedit -set nointegritychecks ON
bcdedit -set loadoptions DDISABLE_INTEGRITY_CHECKS
Restart your system and install the Nostromo Drivers and Loadout Manager"
"Here's how I got my Nostromo to work in Vista 64bit.
Download the v3g or x64 installtions for the Nostromo.
Open MSCONFIG and go to the TOOLS tab. Run down the list until you see "Disable UAC".
Go to the command line in Admin mode and type in either of these commands (depending on the version of Vista you have).
bcdedit -set nointegritychecks ON
bcdedit -set loadoptions DDISABLE_INTEGRITY_CHECKS
Restart your system and install the Nostromo Drivers and Loadout Manager"
Hey, something finally works in Vista Home Premium 64Bit. My N52 has kiss slobber all over it now and the keys actually work. Thanks for the instructions, but it's not for the nub. Your instructions set needs a little tweaking. Just a little more info might help make it a little easier. I've added some help to yours:1. Install the free VistaBootPro program and click the Advanced Settings, select "Microsoft Windows Vista" in the "Select a Windows Vista or Longhorn entry from the list below to begin" area, then put a check mark in the "Disable Vista Driver Signing (64-Bit Only -Requires Restart), and click "Apply Settings" NOTE: I did nothing to any other area but welcome to configure it and other way you like, i.e., I left all other setting as they were when I installed it.
2. No change.
3. If do install N52 from the site he listed, please put it in the same directory (C:/n52) as below so it doesn' confuse you later when you make the profiles then all the Nostromo files and directories are in the same area.
4. Restart as he says. The info here is helpful too.
5. Do like he says: Get lastest beta driver file "Nostromo_x64.msi" from http://files.filefront.com/Nos...4msi...;/fileinfo.html or if it's not available do web search for it.
6. Install it in a directory like C:\n52(same as above), then Start cmd as admin and unpack the *.msi file as he says. You will see Belkin's window, follow instructions just like installing it again.
7. You can do this step another way by going into the motherboard bios(usually by pressing Delete key after doing a Restart) and disable all the USB channels, save, and reboot. But u still need the ps2 kb(you need this to get into the BIOS) and mouse like he says.
8. After you do EXACTLY as he says and you also disabled USB channels, you need to reboot, go into BIOS and enable them.
9. No adds.
I want to thank {T5K}DOZINATOR for some of this info and you can read his take on the procedure at http://www.t5k-clan.com/module...ceae89605448ed374abb90
Again thanks kainlongshot
I actually joined these forums to thank all of you who put info into this thread. I was frustrated at first to see I would have problems with my n52, but was very glad I found this, so thank you to you all.
After last night though, I can actually add something of value to the discussion.
I updated my PC with all of the latest updates, and what do you know...n52 broken again with the drivers reporting they could not load and were potentially corrupted. After doing a good amount of troubleshooting, I finally went back to my logs and looked for an error (which I found in my "Windows logs-->System"):
"Application popup: : \SystemRoot\system32\drivers\bcgame.sys failed to load" (event ID: 26)
I tracked it down to when I installed the updates and at first glance, the only update which seemed to pertain to changing how the n52 would function was:
"Update for Windows Vista for x64-based Systems (KB932596)"
So I uninstalled it. Luckily I was right, and the drivers came back to life after the reboot.
The description of the patch reads:
"An update is availble for Kernel patch protection included with x64-based Windows operating systems. Kernel patch protection protects code and critical structures in the Windows kernel from modification by unknown code or data. After you install this item, you may have to restart your computer."
Hence, if you have problems with your n52 drivers after updating, uninstall the above mentioned patch. Hope this helps!
P.S. - If you don't want Windows Update to keep reminding you of the update, view the available updates, right click it, and choose "Hide update."
After last night though, I can actually add something of value to the discussion.
I updated my PC with all of the latest updates, and what do you know...n52 broken again with the drivers reporting they could not load and were potentially corrupted. After doing a good amount of troubleshooting, I finally went back to my logs and looked for an error (which I found in my "Windows logs-->System"):
"Application popup: : \SystemRoot\system32\drivers\bcgame.sys failed to load" (event ID: 26)
I tracked it down to when I installed the updates and at first glance, the only update which seemed to pertain to changing how the n52 would function was:
"Update for Windows Vista for x64-based Systems (KB932596)"
So I uninstalled it. Luckily I was right, and the drivers came back to life after the reboot.
The description of the patch reads:
"An update is availble for Kernel patch protection included with x64-based Windows operating systems. Kernel patch protection protects code and critical structures in the Windows kernel from modification by unknown code or data. After you install this item, you may have to restart your computer."
Hence, if you have problems with your n52 drivers after updating, uninstall the above mentioned patch. Hope this helps!
P.S. - If you don't want Windows Update to keep reminding you of the update, view the available updates, right click it, and choose "Hide update."
Nice additions so far. There's a lot of good information in this thread. Even more so its got the most views of all the threads in this category.
Perhaps a sticky? I know we aren't the only N52 lovers out there.
Perhaps a sticky? I know we aren't the only N52 lovers out there.
File this as another reason I won't be going to Vista anytime soon. I won't be giving up my N52 anytime soon. They'll have to pry it from my cold hard dead hand to get it away from me. And yes, my hand will certainly be cold and hard by the time the boys from the back get to me since I will have mowed down enemies as far as the eye can see with that pad!
I'll have to swing by the Belkin site (someone posted a link earlier) and leave a comment as to how much I think they suck if they don't write a Vista driver for the N52.
I'll have to swing by the Belkin site (someone posted a link earlier) and leave a comment as to how much I think they suck if they don't write a Vista driver for the N52.
ronach
Senior member
- Oct 9, 1999
- 485
- 2
- 81
deadken wrote,
" File this as another reason I won't be going to Vista anytime soon. I won't be giving up my N52 anytime soon. They'll have to pry it from my cold hard dead hand to get it away from me. And yes, my hand will certainly be cold and hard by the time the boys from the back get to me since I will have mowed down enemies as far as the eye can see with that pad "
My sentiments exactly..heh..I'm still running XP and have a brand new N52 on hand for future use. [ The buttons are hard to push ], not in my opinion..set it up for a game and just simply push em as needed. I'm a 70 year old FPS gamer and do light weight training, maybe that's why I can handle the N52. It is presently being used in Graw2..next victim will be Bioshock.
" File this as another reason I won't be going to Vista anytime soon. I won't be giving up my N52 anytime soon. They'll have to pry it from my cold hard dead hand to get it away from me. And yes, my hand will certainly be cold and hard by the time the boys from the back get to me since I will have mowed down enemies as far as the eye can see with that pad "
My sentiments exactly..heh..I'm still running XP and have a brand new N52 on hand for future use. [ The buttons are hard to push ], not in my opinion..set it up for a game and just simply push em as needed. I'm a 70 year old FPS gamer and do light weight training, maybe that's why I can handle the N52. It is presently being used in Graw2..next victim will be Bioshock.
The issue here isn't caused by Microsoft, it's Belkin's fault. Besides this, I haven't had any issues with Vista-64 bit. It's been super stable and running my games very well (I had to go 64-bit because I have 4gb of RAM).
Overall, there will always be folk who want to cling to the old OS...heck I was stuck on Windows 98 for a long while before I switched over, but it has to happen sometime. It's going to be the new standard, and the faster you get used to it, the more ahead of the curve you are.
Overall, there will always be folk who want to cling to the old OS...heck I was stuck on Windows 98 for a long while before I switched over, but it has to happen sometime. It's going to be the new standard, and the faster you get used to it, the more ahead of the curve you are.
Well, if you went from 98 to ME, then you might understand that newer isn't always better. I don't have a huge issue with the stability of Vista (from what I have heard). I do have issues with 'big brother' watching over me and limiting how I use my PC (some of us do enjoy trying a 'bootleg' program before deciding to buy a copy, please realize that software is non-refundable, etc, etc...). For me a big simple FACT is that there really isn't anything that Vista will do for me that my fully legit WinXP Pro won't do. Perhaps there are things that you need Vista for, but at this point in time I don't. Also, at this time, my gaming would suffer if I switched over to Vista. It seems to be bloated compared to XP Pro.
I wonder if you said the same thing about 64bit XP?? I have 3 64-bit machines running fully legit Win XP Pro, the cost of my "upgrading" all of them would be substanstial. Until Vista wins me over, M$ won't be getting anymore of my money for now.
Your statement about costing a lot of money to upgrade, makes sense. That I can understand, but there really isn't a reason to bash MS over the head for it. You always have a choice, which it sounds like you have. MS is a business like many others. Although I wish they gave OSs for free (sometimes they do, thats how I got mine), thats not how money is made.
You're right, if there is no reason to upgrade then don't upgrade. Nobody is forcing your hand. But know this, no matter how much change sucks, it happens. No doubt MS already has another OS build in the works. Shall we start with the M$ bashing now or should we wait. . .
And a side note, the work around works. Its completely stable and to quote: "mowed down enemies as far as the eye can see with that pad". Check it out if you get the chance. I was skeptical at first myself but found the OS is very friendly and pretty darn stable. One more thing, think about dual booting like I did. You have the best of both worlds then. XP when you need it and Vista when you want to try something new. Again it sounds like money is the issue, which I won't fault you for. But if you do get a chance, check it out with a dual boot. Make the transition super easy.
You're right, if there is no reason to upgrade then don't upgrade. Nobody is forcing your hand. But know this, no matter how much change sucks, it happens. No doubt MS already has another OS build in the works. Shall we start with the M$ bashing now or should we wait. . .
And a side note, the work around works. Its completely stable and to quote: "mowed down enemies as far as the eye can see with that pad". Check it out if you get the chance. I was skeptical at first myself but found the OS is very friendly and pretty darn stable. One more thing, think about dual booting like I did. You have the best of both worlds then. XP when you need it and Vista when you want to try something new. Again it sounds like money is the issue, which I won't fault you for. But if you do get a chance, check it out with a dual boot. Make the transition super easy.
okay guys, we have new Vista 64bit drivers that I'm testing at the moment.
We at belkin arent allowed to release them just yet just to make sure that there arent any bugs in there...have tried them myself and they do work perfectly so hopefully before the end of the month or early September they will be on the belkin.co.uk website.
not a 100% promise but you never know with drivers.
will keep you lot posted and to whom sent emails to belkin UK thanks
We at belkin arent allowed to release them just yet just to make sure that there arent any bugs in there...have tried them myself and they do work perfectly so hopefully before the end of the month or early September they will be on the belkin.co.uk website.
not a 100% promise but you never know with drivers.
will keep you lot posted and to whom sent emails to belkin UK thanks
Wow, thanks Docdutch! Glad to hear progress is being made. You got a lot of N52 fans waiting . . .
Originally posted by: docdutch
okay guys, we have new Vista 64bit drivers that I'm testing at the moment.
We at belkin arent allowed to release them just yet just to make sure that there arent any bugs in there...have tried them myself and they do work perfectly so hopefully before the end of the month or early September they will be on the belkin.co.uk website.
not a 100% promise but you never know with drivers.
will keep you lot posted and to whom sent emails to belkin UK thanks
Will both the N50 and N52 be supported in Vista, or just the latter?
TRENDING THREADS
-
Discussion Zen 5 Speculation (EPYC Turin and Strix Point/Granite Ridge - Ryzen 9000)- Started by DisEnchantment
- Replies: 24K
-
Discussion Intel Meteor, Arrow, Lunar & Panther Lakes Discussion Threads
- Started by Tigerick
- Replies: 20K
-
-
-
Facebook
Twitter