Windows XP Issues

NissanSkylineN1

NissanSkylineN1

3,204
Canada
2.2L Camry
NissanSkylineN1
Xbox??? Who is this Xbox??
Hey guys,

So, I recently decided to dual boot WinXP and Win7 due to networking issues (I use Win7 when my bro is home, using ICS as my internet access, and then using WinXP when his laptop isn't home, using my 32 bit internet adapter driver. I'm too lazy to get a 64 bit one)

I have 3 issues:

1) Its slower than Windows 7. Boot times are faster, and so are shutdown times.But for other things, its much slower. my browser is slower, TF2\CS:S plays slower, CPU related tasks are much slower and more.

2) I'm almost running out of RAM. The 32 bit XP recognizes 3.1 GB of RAM. Apparently theres something called PAE which will increase it up to 4GB. How do I go about doing that?

3) How hard is it to write a 64 bit driver for my adaptor? Its a US Robotics USR5420.

4) Is it possible to run a virtual copy of WinXP 32 bit on my Win7 and make the WinXP recognize the adaptor, and then bridge the 2 OSes?

PC Specs:https://www.gtplanet.net/forum/showthread.php?t=221167
 
Last edited:
Its that same one. Isn't there a possible way for me to virtualize XP on WIn7 64 bit and use the adapter using a bridge?
 
A program like vmware will let you set the virtual computer to use NAT to make it's own IP address and connect to the internet. It works almost every time for me. Though I've seen virtualbox make better use of hardware and I'm almost sure(been a while since I used it) you can use NAT to give the virtual computer an IP address in this program.
 
Not true FerrinoS - they have extended support until April 8, 2014

I hate Windows personally, of all flavors - XP I find to be the least intrusive, Windows 7 to be the most (from a LET ME DO WHAT I FREAKING WANT TO DO standpoint) - but I play video games so what's a guy to do?

WinXP should recognize that adapter just fine. Virtualization is to big a question for me - some devices that don't work on one OS, even if you use the OS that doesn't work as the host, the virtual OS can sometimes work just fine - for me it's trial and error - I would assume there is some deep hardware level stuff you could dissect if you were a virtual dev, but I am not one - so... if it doesn't work initially, it's a hardware compatibility problem. Not as true on Linux/Debian; you're able to fix hardware level issues much easier on those - Windows is very locked down in this regard comparatively.

For your PAE question, add to your boot.ini file the following:

/PAE

And reboot. It still won't address MORE than 4GB, but it will get you to 4GB at least.
 
Last edited:
UPDATE: So I decided to virtualizer, but I couldn't manage to bridge the conections together. I had to use Microsoft Virtualizer with XP Mode.
 

Latest Posts

Back