Please Scroll Down to See Forums Below
Upgrading from XP Home to XP Pro....???
- Thread starter AAP
- Start date
yes it will upgrade it
IT WILL WORK
That's because nobody with a brain would have installed XP Home to begin with. 
If you have another disk or partition it would be wise to back up your data files and possibly your user profile (c:\documents and settings\AAP) to another partition. It'll probably error out when it tries to copy NTUSER.DAT*
If you have another disk or partition it would be wise to back up your data files and possibly your user profile (c:\documents and settings\AAP) to another partition. It'll probably error out when it tries to copy NTUSER.DAT*
Ok... last question... as you may know about the problems I have from my other thread..
http://boards.elitefitness.com/forum/showthread.php?s=&threadid=267291&highlight=XP+Home
Will upgrading this correct it? Or will the Problem just be copied over as well?
http://boards.elitefitness.com/forum/showthread.php?s=&threadid=267291&highlight=XP+Home
Will upgrading this correct it? Or will the Problem just be copied over as well?
A
ajtomasi
Guest
Thing is . . .
Is that disk a corp. edition or a brand new disk? If not, it might not be worth the install, because Microsoft wants everyone to register their xp copy.
Of course there is a way around this
Is that disk a corp. edition or a brand new disk? If not, it might not be worth the install, because Microsoft wants everyone to register their xp copy.
Of course there is a way around this
NoDaddyNo
New member
Why would you want to run Pro or a Server system on your home machine if you aren't going to use any of the features?
Basically it will use more RAM and processor time to do things that you will never use.
Unless you are actually planning on running servers, going to maintain a network more than 10 or so machines, or it is a dual (or more) processor system, or programming applications that need to access those things... then I'm at a loss of why you need it.
I could totally see back in the day when 98 and Me sucked that you would want to step up to higher levels - but even then, you don't need to do a server system.
What exactly are you planning on doing with this? And what sort of machine is this? How much RAM? What sort of processor? How many processors?
Basically it will use more RAM and processor time to do things that you will never use.
Unless you are actually planning on running servers, going to maintain a network more than 10 or so machines, or it is a dual (or more) processor system, or programming applications that need to access those things... then I'm at a loss of why you need it.
I could totally see back in the day when 98 and Me sucked that you would want to step up to higher levels - but even then, you don't need to do a server system.
What exactly are you planning on doing with this? And what sort of machine is this? How much RAM? What sort of processor? How many processors?
AAP said:
you may not have to. if you do pm me
NoDaddyNo
New member
supernav said:
Right on sister.
You always crack me up with yoru authoritative remarks on shit where you toss around a few buzzwords and proclaim that it is all easy and the obvious answer is... and then you say something akin to that we should all bathe in Jello because you like things that have lime flavoring in them.
I have developed on a fairly wide range of things and I have seen nothing that backs up what you say. NT sucked total ass when it first came out - and it sucks now. There was a time when it was stable and good since there was nothing else out there in Windows land better than it, but there is no longer any official MS support for NT anymore, yet there are still holes being found in it.
This would lead me to believe that it is indeed not the perfect OS.
2K was better when it first came out, and it had some nifty features over time. It too got more stable over time, and it is quite a good system. I have a few servers at work running it and I see no need to upgrade them for at least another year, perhaps two.
That said, for a desktop system, 2K currently is lagging behind - it doesn't currently do a single thing that XP can't do right now, and XP (if properly configured) does it faster and with less RAM.
I maintain an office environment with XP clients and Win2K servers.
They each have their place - but to make a blanket statement is just plain silly.
In the end, I don't even really like Windows - but that isn't what this is about.
As far as I can tell, it sounds like AAP is installing an OS over his current one, and this new OS will run applications and services that he does need, which will take up RAM and processor time - all because he has a problem with his network card.
It seems for $20 he could swap in a new bit of hardware and try to resolve if that is the issue and save himself the time and headache of upgrading the system.
I would say that unless AAP is running a dual processor system and is hosting a website or ftp site from his computer, or he is going to be setting up a lan in his place with more than 10 computers (which I'm doubting after seeing that he is a normal user here), there is no real need for him to be using XP Pro - upgrading to that will not necessarily save you any headaches or fix any problems.
If you are going to do that, you might as well backup your important data - format your hard drive, and then just put XP home right back on - it is just a home system that you are using to browse the internet with right?
NoDaddyNo said:
In the beginning someone suggested it was the network card. But then again, wouldn't the net card malfunction randomly and not just when I accessed certain sites? It only happens when I go to certain sites. I can leave the PC running all week and never have the internet crash or disconnect. But 3 seconds after going to delta.com, ajc.com, sunsentinel.com, or a few more specific ones, it crashes. A network card would not be this precise in crashing on cue.
NoDaddyNo
New member
AAP said:
So the answer is then to install a new operating system that will run servers that you won't even use?
If you are going to go through the hour long install process - backup what you need from your computer, format everything, and install fresh your XP Home back onto the machine.
Have you done a reinstall of the OS overtop of what you have now? Although technically with most of the updates now this shouldn't really matter since they replace a lot of that.
NoDaddyNo said:
Bro, I don't know what the answer is. I honestly don't. I have tried every single thing that was suggested to me by the guys on here and the tech geeks at work. And nothing has worked man. I am frustrated beyond belief. It would not be so bad, but some of those websites like delta.com and hotmail.com are crucial to me.
I am open to any and all suggestions on how to fix this.
NoDaddyNo
New member
The process should be that you have some connection to your ISP (cable modem or DSL - I forget which you said) and then that comes in either through a router/firewall, or directly into your network card.
The ISP gives you an IP address that the world sees you as (likely dynamically - you really never hear of getting a static one anymore - although if you watch, you frequently will renew the same IP over and over in the lease) connect to the net.
Your machine can then use this IP address as well as the DNS info that is sent to it to go out and find domains and urls that you put into your browser (there is much more than this, but from your perspective, I would imagine the net is largely just the web and email which likely blend together before you).
When you visited a page, the network went down - you then did a "ping www.yahoo.com" and that came up with zilch.
That could mean that either you lost your IP lease, or that your DNS servers were not responding (they are frequently hit by DOS attacks).
But that was ruled out by the fact that you did an "ipconfig /release" and an "ipconfig /renew" (the second of which didn't matter once we saw the error for the first - after that they were going to get the same error).
It told you that no media was connected to your network card.
Now, your network card worked up until that point - and there is no reason why it should bomb out on certain pages....
This sounds like it is your cable modem/DSL, or something with that company.
Can you put another machine on that connection and surf to the same pages and many more with no hassles?
Can you take that exact machine to another network connection from a different provider and have it hit those connections?
As far as I can tell, until you can show that it is definitely your machine - I would suspect the ISP and their connection to you moreso than your machine.
(I didn't read every single one of your posts, so if you have already shown how you did this, excuse me)
The ISP gives you an IP address that the world sees you as (likely dynamically - you really never hear of getting a static one anymore - although if you watch, you frequently will renew the same IP over and over in the lease) connect to the net.
Your machine can then use this IP address as well as the DNS info that is sent to it to go out and find domains and urls that you put into your browser (there is much more than this, but from your perspective, I would imagine the net is largely just the web and email which likely blend together before you).
When you visited a page, the network went down - you then did a "ping www.yahoo.com" and that came up with zilch.
That could mean that either you lost your IP lease, or that your DNS servers were not responding (they are frequently hit by DOS attacks).
But that was ruled out by the fact that you did an "ipconfig /release" and an "ipconfig /renew" (the second of which didn't matter once we saw the error for the first - after that they were going to get the same error).
It told you that no media was connected to your network card.
Now, your network card worked up until that point - and there is no reason why it should bomb out on certain pages....
This sounds like it is your cable modem/DSL, or something with that company.
Can you put another machine on that connection and surf to the same pages and many more with no hassles?
Can you take that exact machine to another network connection from a different provider and have it hit those connections?
As far as I can tell, until you can show that it is definitely your machine - I would suspect the ISP and their connection to you moreso than your machine.
(I didn't read every single one of your posts, so if you have already shown how you did this, excuse me)
first back up your files on your computer to cd or whatever you got. when you install your xp pro, choose new installation over upgrade. you will lose your files on your computer. not irreversably but may be difficult to get them back. so BACK UP what you need. install your xp pro in the same folder c:\windows, it will say everything will be lost blah blah blah. go for ntfs formatting. if you don't already have it. check your PM in about 5 minutes too
pitbullstl
New member
jnuts said:
Or do what I did.....after calling Dell "Otherwise known as English as a second language learning center" and speaking to not one but three different broken English speaking tech support guys, I finally got ahold of somone in charge of customer service.....documented to them I had purchased 5 desktops with extended warranties, and told them they could take my machine back, and send out a brand new one sans XP.....or they could get my machine back "ticking"......they saw the light and sent me a brand new desktop...........
NoDaddyNo
New member
The difference is no real difference between XP Home and XP Pro in terms of the base code - XP Pro has servers built into it that home doesn't have, and it can handle multiple processors.
You are wasting time, effort, and resources if you upgrade to XP Pro.
The differences between Home and Pro are:
-Pro has the Remote Desktop Client straight out of the box - but you can download it for free and install it on any XP machine - even Home.
-Home supports one processor, Pro supports two
-Pro has the automated system recovery (which I've found not to be so great) and Home doesn't - but it is on the CD, you can add it
-Pro has "dynamic disk support" - you don't need this
-Home doesn't have fax built in straight out of the box, but Pro does. It is on the CD for Home and you can install it if you want (noticing a pattern here?)
-Pro has IIS 5.1 - but I don't think you need to run any websites or ftp sites from your machine.
-Pro supports an encrypted file system (this slows your system down)
-Pro has file level access control - which doesn't matter unless it is a machine that multiple people are using and it matters who can see what
-Home allow you to join an Active Directory network tree
-Pro has a lot of other crap that you honestly don't need at all (like clients for Netware services, and 64-bit CPU support)
The only real benefit I can see from putting Pro on would be to get the Network Monitor to try to track down what this issue is - and even then, I've used that before and it isn't usually terribly helpful if the machine itself is having the problem.
I'll talk to one of our tech support guys today and see if he can think of anything.
I say format it all (after saving out whatever it is that you want to keep) and then reinstall Home - which you have a legal copy of.
Unless you have a dual processor machine with at least half a gig of memory (and I would say a gig is better), then don't bother with using Pro.
It will run on far less, but without at least 512M RAM, it is going to be annoying.
You are wasting time, effort, and resources if you upgrade to XP Pro.
The differences between Home and Pro are:
-Pro has the Remote Desktop Client straight out of the box - but you can download it for free and install it on any XP machine - even Home.
-Home supports one processor, Pro supports two
-Pro has the automated system recovery (which I've found not to be so great) and Home doesn't - but it is on the CD, you can add it
-Pro has "dynamic disk support" - you don't need this
-Home doesn't have fax built in straight out of the box, but Pro does. It is on the CD for Home and you can install it if you want (noticing a pattern here?)
-Pro has IIS 5.1 - but I don't think you need to run any websites or ftp sites from your machine.
-Pro supports an encrypted file system (this slows your system down)
-Pro has file level access control - which doesn't matter unless it is a machine that multiple people are using and it matters who can see what
-Home allow you to join an Active Directory network tree
-Pro has a lot of other crap that you honestly don't need at all (like clients for Netware services, and 64-bit CPU support)
The only real benefit I can see from putting Pro on would be to get the Network Monitor to try to track down what this issue is - and even then, I've used that before and it isn't usually terribly helpful if the machine itself is having the problem.
I'll talk to one of our tech support guys today and see if he can think of anything.
I say format it all (after saving out whatever it is that you want to keep) and then reinstall Home - which you have a legal copy of.
Unless you have a dual processor machine with at least half a gig of memory (and I would say a gig is better), then don't bother with using Pro.
It will run on far less, but without at least 512M RAM, it is going to be annoying.
XBiker
Well-known member
It's one of three things here.
1. Your ISP
2. Your machine (hardware)
3. Your software
You have ruled out 1 with the laptop.
You have partially ruled out 2. (Your network adapter cannot tell that you are visiting hotmale.com, delta.com, or whatever. To the NIC, a packet of data is just that, a packet of data.) However, memory can do some screwy things to your system if it's not working correctly or you have a bad stick of it.
Many things point to 3, but not exclusively.
IMO, buy the legit copy of XP Pro, backup and reload the system.
1. Your ISP
2. Your machine (hardware)
3. Your software
You have ruled out 1 with the laptop.
You have partially ruled out 2. (Your network adapter cannot tell that you are visiting hotmale.com, delta.com, or whatever. To the NIC, a packet of data is just that, a packet of data.) However, memory can do some screwy things to your system if it's not working correctly or you have a bad stick of it.
Many things point to 3, but not exclusively.
IMO, buy the legit copy of XP Pro, backup and reload the system.
Similar threads
