Update Loop Failure
Just FYI, my operating system is XP Version 2002, Service Pack 2.
But really, it took me a while to find out where to get that info. Is it possible to revise your stickied template to indicate to people where they can find all the technical info you need to troubleshoot problems (just make it a parenthetical within each line of the template).
But really, it took me a while to find out where to get that info. Is it possible to revise your stickied template to indicate to people where they can find all the technical info you need to troubleshoot problems (just make it a parenthetical within each line of the template).
The problem with that is that it depends on the OS /mrgreen.gif" style="vertical-align:middle" emoid=":D" border="0" alt="mrgreen.gif" /> so all explanations would get REALLY long and confusing.LostChild wrote:QUOTE (LostChild @ Apr 11 2008, 09:58 PM) Just FYI, my operating system is XP Version 2002, Service Pack 2.
But really, it took me a while to find out where to get that info. Is it possible to revise your stickied template to indicate to people where they can find all the technical info you need to troubleshoot problems (just make it a parenthetical within each line of the template).
History doesn't like to repeat himself.
my os is xp
dont know any of the other stuff tho
dont know any of the other stuff tho
Never give up.
Even when all seems hopeless, don't give up.
If you keep fighting, losing is only a possibility.
If you give up, losing is a guarantee.
Never give up. -Beez
Even when all seems hopeless, don't give up.
If you keep fighting, losing is only a possibility.
If you give up, losing is a guarantee.
Never give up. -Beez
HSharp wrote:QUOTE (HSharp @ Apr 18 2009, 03:15 PM) I was deadly serious about Buyo and him almost being thawrted by a probe wall, had there been better probe spammage on that green door that exp would have not gotten capped.
Simple way to find out your OS:LostChild wrote:QUOTE (LostChild @ Apr 11 2008, 09:58 PM) Just FYI, my operating system is XP Version 2002, Service Pack 2.
But really, it took me a while to find out where to get that info. Is it possible to revise your stickied template to indicate to people where they can find all the technical info you need to troubleshoot problems (just make it a parenthetical within each line of the template).
1. Save everything you're working on ATM.
2. Reboot computer.
3. Read the OS name off the startup screen.
I mean c'mon, you HAVE booted up your machine at least once, haven't you? /wink.gif" style="vertical-align:middle" emoid=";)" border="0" alt="wink.gif" />
No History, it's pretty damn simple and straightforward /wink.gif" style="vertical-align:middle" emoid=";)" border="0" alt="wink.gif" />History wrote:QUOTE (History @ Apr 11 2008, 10:16 PM) The problem with that is that it depends on the OS /mrgreen.gif" style="vertical-align:middle" emoid=":D" border="0" alt="mrgreen.gif" /> so all explanations would get REALLY long and confusing.
I asked for OS versions, because there is other problem, that seems to be purely Win 98 related. No update on your problem for now
Uninstalling Alleg and .NET 2.0 and re-installing .NET1.1 and Alleg with manual ASGS files overwrite seems to have worked.
I was WinXP by the way.
PS. Don't forget to save your artwork folder and then overwrite it, saves time.
I was WinXP by the way.
PS. Don't forget to save your artwork folder and then overwrite it, saves time.
One short sleep past, we wake eternally and Death shalt be no more; Death, thou shalt die! 
But Ogor, that would require someone to reboot their computer right at the exact moment they're trying to fill out your template. The easier way is to simply open control panel, double click on system and read what it says : P
Regarding the uninstall, I play from a company laptop and I would hesitate to uninstall NetFramework 1.1. As I recall (please pay attention o great developer of the fancy new netframework compatible 2.0 system, a.k.a Pook), when I first went to install Allegiance on this laptop and tried to install netframework, it told me I didn't have access rights. Thankfully, as it turns out, it already had 1.1 onboard. But I doubt I'll be able to install 2.0 if that's going to be the requirement.
(The only caveat is that was months ago, and I just vaguely recall that it wouldn't let me install it... maybe I had been trying to install 2.0 and it wouldn't let me, who knows).
Regarding the uninstall, I play from a company laptop and I would hesitate to uninstall NetFramework 1.1. As I recall (please pay attention o great developer of the fancy new netframework compatible 2.0 system, a.k.a Pook), when I first went to install Allegiance on this laptop and tried to install netframework, it told me I didn't have access rights. Thankfully, as it turns out, it already had 1.1 onboard. But I doubt I'll be able to install 2.0 if that's going to be the requirement.
(The only caveat is that was months ago, and I just vaguely recall that it wouldn't let me install it... maybe I had been trying to install 2.0 and it wouldn't let me, who knows).
I currently have .net 2.0, and it still comes up with this problem
so it's not that...
so it's not that...
Never give up.
Even when all seems hopeless, don't give up.
If you keep fighting, losing is only a possibility.
If you give up, losing is a guarantee.
Never give up. -Beez
Even when all seems hopeless, don't give up.
If you keep fighting, losing is only a possibility.
If you give up, losing is a guarantee.
Never give up. -Beez
HSharp wrote:QUOTE (HSharp @ Apr 18 2009, 03:15 PM) I was deadly serious about Buyo and him almost being thawrted by a probe wall, had there been better probe spammage on that green door that exp would have not gotten capped.
As ImZ says. Although .NET 2.0 without SP worked until recently (I know because I updated to be ready for the transition) it no longer works. So the solution is to uninstall 2.0 (possibly using the cleanup tool mentioned here) and installBeez wrote:QUOTE (Beez @ Apr 12 2008, 01:51 AM) I currently have .net 2.0, and it still comes up with this problem
so it's not that...
.Net1.1
Yes this might cause other programs to fail, and it might be better for you to wait for the ASGS upgrade to .NET 2.
History doesn't like to repeat himself.