If you paid attention, I was asking if anyone ran into the same problem to make sure it is related to the hardware of the Latitude X300 rather than a software conflict.
If you don't feel that you like to test it on your system, that is fine. No need to come in here to preach how it should happen.
I posted the question in the Microsoft newsgroup and it seemed that no one was experiencing the problem I received. So I wanted to see if it is related to the hardware I have.
I posted the question in the Microsoft newsgroup and it seemed that no one was experiencing the problem I received. So I wanted to see if it is related to the hardware I have.
-Glenn
The error message you posted occurs on systems which don't even have RC-2 of SP-2 installed, so it could be reasonably argued that it has nothing necessarily to do with the combination of an X-300 and RC-2. It's a software related error message (and 3rd party software, at that), and the software is in mainstream use. While it may be occurring in this instance as a result of your installation of RC-2 on an X-300, it's by no means anything that would necessarily occur exclusively under those operating conditions, as a simple Google search will certainly confirm. It could very well be the result of a conflict with other software you have installed.
Ed C has made a valid point. It could be argued that as a general rule, this particular forum doesn't do much toward discouraging rather reckless acts such as installing beta software on non-test platforms, but in this case, the response was more than appropriate.
The WinXP firewall as-is (yes, there's already a firewall on XP) is more than sufficient to keep your system protected. The firewall in its current state (without SP-2 RC-2), in conjunction with an up to date, properly configured anti virus application, along with responsible user practices (i.e., avoiding known junk/spyware installation, regular updates at Windows Update, etc.) is perfectly serviceable. Release candidate/beta software is not intended for general use, plain and simple. It's not necessarily safe, nor is it necessarily going to work on mainstream systems the way the final public release version might. Unless you are actively involved in the testing of beta software for development/research purposes, and as has been noted many times in many places, you are asking for trouble by installing it. The fact that you're posting here would seem to indicate that you're not actively involved in beta testing/legitimate research, because anyone who was would not be in here wondering aloud why an unproven, uncertified pre-release version of software wasn't working.
I did pay attention, and I maintain my previous observation that if you're asking a question of this nature in this sort of a forum, rather than one that is devoted specifically to beta testing issues, and if you're making statements about firewalls that already exist in the release version of Windows XP such as the one in your second post in this thread, you are more than likely going to be much better off taking yourself out of the Volunteer Beta Testing pool.
"WHY? Cause Microsoft has added a lot of new features including a firewall."
News Flash: The firewall has been there since the final release was made available for sale to the general public.
Uninstalling XPSP2 RC2 resolved the problem...so that is why I wanted to see if anyone else ran into the same problem. The laptop is fairly new and not much was added, so I assume others who installed SP2 would see the problem too...
Ed C
2 Intern
•
3.2K Posts
0
June 18th, 2004 00:00
gdoes
37 Posts
0
June 18th, 2004 01:00
WHY? Cause Microsoft has added a lot of new features including a firewall.
Maybe you are waiting for the day that hackers will take over your PC
instead of actively making sure you have all the latest patches on your computer.
-Glenn
Ed C
2 Intern
•
3.2K Posts
0
June 18th, 2004 01:00
No I'm waiting until it becomes a OFFICIAL release NOT BETA. And then I'll wait a little longer for the last bugs to be worked out.
I have no idea what you use a computer for but I use mine to make living.
gdoes
37 Posts
0
June 18th, 2004 02:00
I have no idea why you responded to this thread when you have nothing useful to contribute?
-Glenn
gdoes
37 Posts
0
June 18th, 2004 14:00
If you paid attention, I was asking if anyone ran into the same problem to make sure it is related to the hardware of the Latitude X300 rather than a software conflict.
If you don't feel that you like to test it on your system, that is fine. No need to come in here to preach how it should happen.
-Glenn
gdoes
37 Posts
0
June 18th, 2004 14:00
I posted the question in the Microsoft newsgroup and it seemed that no one was experiencing the problem I received. So I wanted to see if it is related to the hardware I have.
-Glenn
Flooby
2 Intern
•
3K Posts
0
June 18th, 2004 14:00
The error message you posted occurs on systems which don't even have RC-2 of SP-2 installed, so it could be reasonably argued that it has nothing necessarily to do with the combination of an X-300 and RC-2. It's a software related error message (and 3rd party software, at that), and the software is in mainstream use. While it may be occurring in this instance as a result of your installation of RC-2 on an X-300, it's by no means anything that would necessarily occur exclusively under those operating conditions, as a simple Google search will certainly confirm. It could very well be the result of a conflict with other software you have installed.
http://www.aspack.com/asprotect.htm
http://www.splitcamera.com/guestbook/guestbook.php?act=show&page=6 (See post 72)
Flooby
2 Intern
•
3K Posts
0
June 18th, 2004 14:00
Ed C has made a valid point. It could be argued that as a general rule, this particular forum doesn't do much toward discouraging rather reckless acts such as installing beta software on non-test platforms, but in this case, the response was more than appropriate.
The WinXP firewall as-is (yes, there's already a firewall on XP) is more than sufficient to keep your system protected. The firewall in its current state (without SP-2 RC-2), in conjunction with an up to date, properly configured anti virus application, along with responsible user practices (i.e., avoiding known junk/spyware installation, regular updates at Windows Update, etc.) is perfectly serviceable. Release candidate/beta software is not intended for general use, plain and simple. It's not necessarily safe, nor is it necessarily going to work on mainstream systems the way the final public release version might. Unless you are actively involved in the testing of beta software for development/research purposes, and as has been noted many times in many places, you are asking for trouble by installing it. The fact that you're posting here would seem to indicate that you're not actively involved in beta testing/legitimate research, because anyone who was would not be in here wondering aloud why an unproven, uncertified pre-release version of software wasn't working.
Message Edited by Flooby on 06-18-2004 11:03 AM
Flooby
2 Intern
•
3K Posts
0
June 18th, 2004 14:00
I did pay attention, and I maintain my previous observation that if you're asking a question of this nature in this sort of a forum, rather than one that is devoted specifically to beta testing issues, and if you're making statements about firewalls that already exist in the release version of Windows XP such as the one in your second post in this thread, you are more than likely going to be much better off taking yourself out of the Volunteer Beta Testing pool.
"WHY? Cause Microsoft has added a lot of new features including a firewall."
News Flash: The firewall has been there since the final release was made available for sale to the general public.
gdoes
37 Posts
0
June 18th, 2004 15:00
Uninstalling XPSP2 RC2 resolved the problem...so that is why I wanted to see if anyone else ran into the same problem. The laptop is fairly new and not much was added, so I assume others who installed SP2 would see the problem too...
-Glenn