Sometime back in 2006, I got this working on WinXP 64-bit. Xbox Neighbourhood is a 32-bit shell extension, so it takes a little bit more work to get it running. And now, I'm running Windows 8 64-bit, and I can't remember what I had to do. There was a thread I started on Xbox-Scene's forums years ago, but that forum is now dead, and not even archive.org could save it (well much of it), so I'm frantically trying to rediscover that post and when I started that thread. In the mean time, does anyone here remember? If so, please share. Thanks. Shogun. EDIT: For those of you who are going to suggest a VM of WinXP 32-bit, I tried that. Everything works except for the debugger, which is critical.
God that would be fantastic if someone can remember. I hate having to dig my old POS PC out to use the original Neighborhood.
Seems odd that the debugger wouldn't work in a VM. Here's hoping you (or somebody else) remembers how it is done.
The VM problem was DNS related as far as I know. I remember fixing it using C:\windows\system32\etc\hosts and adding the xbox by name using regedit in the past - but I couldn't get it working this time. I solved the issue by simply switching to a bridged network rather than NAT in VirtualBox. This works fine for me (but I should probably have stronger anti-virus now)
What JayFoxRox said. Works for me too. I never got Xbox neighborhood working in Win7. I figured the shell extension was incompatible. I think I got it working on Vista before using the modification Eviltaco64 posted.
WinXP will not install on a Mac Pro, I tried it. Sorry, forgot to mention that. Yyyyyyyeeeessssssssss! That's it! Although I kinda doubt this will work on Win8, it's worth a try anyway. The guys at emuxtras are suggesting the same thing. Will try that as soon as I track down the bad RAM in my Mac (it decided to die last night, so it won't even start). I got it working in Vista (32-bit), but it was awful (lots of random errors during network transfers, had to right click -> Open for every folder). If it won't work for Win7, I'm quite sure it won't work for Win8. I'll never know until I try though. Shogun.
To get around all of the annoying errors with xbox neighborhood I just use the command line tools that are provided with the XDK to transfer files, I had way more success that way.
Please do you know if Visual studio 2003 works on 64 bit windows 8? VS 2003 is the only way to compil .xbe
Xbox Neighbourhood isn't working, even with the fix from xbox-scene. "This file does not have a program associated with it for performing this action. Please install a program or, if one is already installed, create an association in the Default Programs control Panel." I'm going to look into this further... EDIT: Wtf is "Default Programs" in control panel? This is just another reminder of what I hate about Windows ever since Vista. Even MacOSX is more straight forward than this... Which tool are you referring to? You mean with xbdir? I tried that, but without Xbox Neighbourhood, I don't know how to setup an Xbox network. 1. For me, it works, but with multiple bugs. It will be hard to create a new project because the menu is kinda broken, and a few other things I don't quite remember. Just remember that Windows 8 gives you the compatibility warning prior to running it for a reason. 2. No, .net 2003 is not the only way to compile. If you have the XDK 4627 or earlier, you can use Visual Studio 6.0. Also, there's alternative ways like using the commend line, but that's not so user friendly. Shogun. EDIT2: Anyone else here able to get the debugger working in VirtualBox?
? Yes. I'm using VirtualBox and debugging works, PIX works, neighbourhood works - everything works.. There are probably 3 solutions: VirtualBox using... 1. a bridged network 2. NAT with proper DNS configuration 3. using some mad hacks in the registry and system directory to fake and fool DNS and NetBIOS or something You acknowledged the existence of solution #1 earlier: Note that a bridged network will put your VM in the network. Most likely this means: internet. Which (for XP) means: frequent shutdowns because of trojans, viruses etc. So you should probably bump up your security in the VM bigtime and probably block most ports on the host already. Also you'd want to disable any write access to your host directories - possibly even read so nothing can be stolen. Personally I like to think of myself as a pretty badass guy: I don't use any AV and just reset my machine when it is infected. If anyone steals data I'll be fucked - but at least I'm not one of those paranoid AV wimps. (= I'm too lazy to setup AV and scared shitless everytime my VM is online [but I'm too badass to admit that])
