We're doomed.sweener2001 wrote:like sublimation?neo_bahamut1985 wrote:I know. What about it? Your calling me that doesn't phase me at all.
retard
let's all remember that this is a tech support person
PJ64 1.x doesn't like WinXP reinstallations it seems
Moderator: General Mods
-
- ZSNES Developer
- Posts: 6747
- Joined: Tue Dec 28, 2004 6:47 am
-
- Trooper
- Posts: 369
- Joined: Tue Jun 10, 2008 6:19 am
- Location: Australia
- Contact:
-
- Inmate
- Posts: 1751
- Joined: Mon Dec 06, 2004 7:47 am
- Location: WA
-
- Buzzkill Gil
- Posts: 4295
- Joined: Wed Jan 12, 2005 7:14 pm
-
- Trooper
- Posts: 369
- Joined: Tue Jun 10, 2008 6:19 am
- Location: Australia
- Contact:
Most of them ARE actually, depending on their installed location, and exactly what OS you are reinstalling.Gil_Hamilton wrote:Most emulators AREN'T, actually.Squall_Leonhart wrote:Leave him be, Emulators are one a few programs that are sensitive to System changes, like reinstalls.
[img]http://img.photobucket.com/albums/v253/squall_leonhart69r/Final_Fantasy_8/squall_sig1.gif[/img]
[url=http://vba-m.com/]VBA-M Forum[/url], [url=http://www.ngohq.com]NGOHQ[/url]
[url=http://vba-m.com/]VBA-M Forum[/url], [url=http://www.ngohq.com]NGOHQ[/url]
-
- Buzzkill Gil
- Posts: 4295
- Joined: Wed Jan 12, 2005 7:14 pm
The only thing that even has potential to be an issue in most cases is the file path.Squall_Leonhart wrote:Most of them ARE actually, depending on their installed location, and exactly what OS you are reinstalling.Gil_Hamilton wrote:Most emulators AREN'T, actually.Squall_Leonhart wrote:Leave him be, Emulators are one a few programs that are sensitive to System changes, like reinstalls.
And changing paths will break damn near everything, though it's a lot easier to fix in emulators(Hey, my Open Rawmz window has a file browser!).
-
- Trooper
- Posts: 369
- Joined: Tue Jun 10, 2008 6:19 am
- Location: Australia
- Contact:
Gil_Hamilton wrote:The only thing that even has potential to be an issue in most cases is the file path.Squall_Leonhart wrote:Most of them ARE actually, depending on their installed location, and exactly what OS you are reinstalling.Gil_Hamilton wrote:Most emulators AREN'T, actually.Squall_Leonhart wrote:Leave him be, Emulators are one a few programs that are sensitive to System changes, like reinstalls.
And changing paths will break damn near everything, though it's a lot easier to fix in emulators(Hey, my Open Rawmz window has a file browser!).
LOL, well, had this been vista, reinstalling it would've re-enabled UAC, and if the emulator was in program files, like it installs to by default, it would fail to work.
[img]http://img.photobucket.com/albums/v253/squall_leonhart69r/Final_Fantasy_8/squall_sig1.gif[/img]
[url=http://vba-m.com/]VBA-M Forum[/url], [url=http://www.ngohq.com]NGOHQ[/url]
[url=http://vba-m.com/]VBA-M Forum[/url], [url=http://www.ngohq.com]NGOHQ[/url]
-
- Buzzkill Gil
- Posts: 4295
- Joined: Wed Jan 12, 2005 7:14 pm
A. It WASN'T Vista.Squall_Leonhart wrote:Gil_Hamilton wrote:The only thing that even has potential to be an issue in most cases is the file path.Squall_Leonhart wrote:Most of them ARE actually, depending on their installed location, and exactly what OS you are reinstalling.Gil_Hamilton wrote:Most emulators AREN'T, actually.Squall_Leonhart wrote:Leave him be, Emulators are one a few programs that are sensitive to System changes, like reinstalls.
And changing paths will break damn near everything, though it's a lot easier to fix in emulators(Hey, my Open Rawmz window has a file browser!).
LOL, well, had this been vista, reinstalling it would've re-enabled UAC, and if the emulator was in program files, like it installs to by default, it would fail to work.
B. MOST emulators don't HAVE an install procedure.
-
- Trooper
- Posts: 369
- Joined: Tue Jun 10, 2008 6:19 am
- Location: Australia
- Contact:
Both counts being true, the fact remains that a change to the windows environment CAN effect pj64, and since this topic is about pj64, and a crash bug that was occuring with it, it still remains a valid point to raise.Gil_Hamilton wrote:A. It WASN'T Vista.
B. MOST emulators don't HAVE an install procedure.
[img]http://img.photobucket.com/albums/v253/squall_leonhart69r/Final_Fantasy_8/squall_sig1.gif[/img]
[url=http://vba-m.com/]VBA-M Forum[/url], [url=http://www.ngohq.com]NGOHQ[/url]
[url=http://vba-m.com/]VBA-M Forum[/url], [url=http://www.ngohq.com]NGOHQ[/url]
-
- Inmate
- Posts: 1751
- Joined: Mon Dec 06, 2004 7:47 am
- Location: WA
-
- Trooper
- Posts: 369
- Joined: Tue Jun 10, 2008 6:19 am
- Location: Australia
- Contact:
-
- Trooper
- Posts: 369
- Joined: Tue Jun 10, 2008 6:19 am
- Location: Australia
- Contact:
....to about 1,000,000 after that i forget that theres hundreds of millions and thousands of millions before it reachs a billion.odditude wrote:how high can you count?Squall_Leonhart wrote:how many times has he done this before?
[img]http://img.photobucket.com/albums/v253/squall_leonhart69r/Final_Fantasy_8/squall_sig1.gif[/img]
[url=http://vba-m.com/]VBA-M Forum[/url], [url=http://www.ngohq.com]NGOHQ[/url]
[url=http://vba-m.com/]VBA-M Forum[/url], [url=http://www.ngohq.com]NGOHQ[/url]
-
- Buzzkill Gil
- Posts: 4295
- Joined: Wed Jan 12, 2005 7:14 pm
Squall_Leonhart wrote:Both counts being true, the fact remains that a change to the windows environment CAN effect pj64, and since this topic is about pj64, and a crash bug that was occuring with it, it still remains a valid point to raise.Gil_Hamilton wrote:A. It WASN'T Vista.
B. MOST emulators don't HAVE an install procedure.
Not in this form:
Squall_Leonhart wrote:Leave him be, Emulators are one a few programs that are sensitive to System changes, like reinstalls.
And besides, given Bahumat changed motherboards without reinstalling Windows, THEN blamed the bugs on a bad motherboard, and changed boards AGAIN... he's still riding that wave.
-
- Trooper
- Posts: 369
- Joined: Tue Jun 10, 2008 6:19 am
- Location: Australia
- Contact:
This install of windows im running right now is from 2005, survived a change from a KT600 to a Nforce 2, its very easy to do really, I also enabled APIC without a reinstall of windows using devcon tricksGil_Hamilton wrote:Squall_Leonhart wrote:Both counts being true, the fact remains that a change to the windows environment CAN effect pj64, and since this topic is about pj64, and a crash bug that was occuring with it, it still remains a valid point to raise.Gil_Hamilton wrote:A. It WASN'T Vista.
B. MOST emulators don't HAVE an install procedure.
Not in this form:Squall_Leonhart wrote:Leave him be, Emulators are one a few programs that are sensitive to System changes, like reinstalls.
And besides, given Bahumat changed motherboards without reinstalling Windows, THEN blamed the bugs on a bad motherboard, and changed boards AGAIN... he's still riding that wave.

check out ngohq's software section, or ngohq's, i've put guides for the mainboard swap and apic enabling there.
[img]http://img.photobucket.com/albums/v253/squall_leonhart69r/Final_Fantasy_8/squall_sig1.gif[/img]
[url=http://vba-m.com/]VBA-M Forum[/url], [url=http://www.ngohq.com]NGOHQ[/url]
[url=http://vba-m.com/]VBA-M Forum[/url], [url=http://www.ngohq.com]NGOHQ[/url]
...but you know what you're doing and how to research things if you don't. there's a key difference there.Squall_Leonhart wrote:This install of windows im running right now is from 2005, survived a change from a KT600 to a Nforce 2, its very easy to do really, I also enabled APIC without a reinstall of windows using devcon tricksGil_Hamilton wrote:Squall_Leonhart wrote:Both counts being true, the fact remains that a change to the windows environment CAN effect pj64, and since this topic is about pj64, and a crash bug that was occuring with it, it still remains a valid point to raise.Gil_Hamilton wrote:A. It WASN'T Vista.
B. MOST emulators don't HAVE an install procedure.
Not in this form:Squall_Leonhart wrote:Leave him be, Emulators are one a few programs that are sensitive to System changes, like reinstalls.
And besides, given Bahumat changed motherboards without reinstalling Windows, THEN blamed the bugs on a bad motherboard, and changed boards AGAIN... he's still riding that wave.
check out ngohq's software section, or ngohq's, i've put guides for the mainboard swap and apic enabling there.
Why yes, my shift key *IS* broken.
-
- Trooper
- Posts: 369
- Joined: Tue Jun 10, 2008 6:19 am
- Location: Australia
- Contact:

[img]http://img.photobucket.com/albums/v253/squall_leonhart69r/Final_Fantasy_8/squall_sig1.gif[/img]
[url=http://vba-m.com/]VBA-M Forum[/url], [url=http://www.ngohq.com]NGOHQ[/url]
[url=http://vba-m.com/]VBA-M Forum[/url], [url=http://www.ngohq.com]NGOHQ[/url]
-
- -Burninated-
- Posts: 871
- Joined: Mon Sep 10, 2007 11:33 pm
- Location: Unspecified
Then someone needs to do some explaining. Why is it that when I got motherboard B, the NIC worked right out of the box, without an Windows XP reinstall? Then why was it that with the first motherboard, the NIC didn't work out of the box, and did do an XP reinstall? I know that had I listened and just reinstalled the XP, the issue would've likely gone away, and wouldn't have had my head been bitten off, but that's all in the past and I have a new motherboard (which everything works flawlessly) and could everyone just stop freakin' reminding me about the whole bloody thing?Gil_Hamilton wrote:
And besides, given Bahumat changed motherboards without reinstalling Windows, THEN blamed the bugs on a bad motherboard, and changed boards AGAIN... he's still riding that wave.
Can't we just put this in the past or am I so doomed as to never have a day go by where someone doesn't remind me about it? Yes I admit I don't know everything and yes, I made several mistakes, so, there you have it.
Last edited by neo_bahamut1985 on Mon Dec 22, 2008 1:06 am, edited 1 time in total.
俺はテメエの倒す男だ! 宜しく! お前はもう死んでいる...
-
- Inmate
- Posts: 1751
- Joined: Mon Dec 06, 2004 7:47 am
- Location: WA
-
- Buzzkill Gil
- Posts: 4295
- Joined: Wed Jan 12, 2005 7:14 pm
As I said... without any way whatsoever of finding out what the hell you were doing, my best is that the new motherboard is more closely related to the old one.neo_bahamut1985 wrote: Then someone needs to do some explaining. Why is it that when I got motherboard B, the NIC worked right out of the box, without an Windows XP reinstall? Then why was it that with the first motherboard, the NIC didn't work out of the box, and did do an XP reinstall?
You disproved your own hypothesis that the network problems were a bad ethernet controller on the motherboard with the PCI ethernet controller(that and other users of the board confirmed it was acting exactly like it was supposed to without drivers).
And one of the few things I'm DAMN sure of is that you didn't have a completely non-functional PCI bus.
Therefore, it was a software issue.
It's still fresh.I know that had I listened and just reinstalled the XP, the issue would've likely gone away, and wouldn't have had my head been bitten off, but that's all in the past and I have a new motherboard (which everything works flawlessly) and could everyone just stop freakin' reminding me about the whole bloody thing?
Can't we just put this in the past or am I so doomed as to never have a day go by where someone doesn't remind me about it? Yes I admit I don't know everything and yes, I made several mistakes, so, there you have it.
Soon you'll do something else, and we'll harass you about that.
-
- Trooper
- Posts: 369
- Joined: Tue Jun 10, 2008 6:19 am
- Location: Australia
- Contact:
Your trying to find out if he'll snap and commit forum suicide, aren't youGil_Hamilton wrote:As I said... without any way whatsoever of finding out what the hell you were doing, my best is that the new motherboard is more closely related to the old one.neo_bahamut1985 wrote: Then someone needs to do some explaining. Why is it that when I got motherboard B, the NIC worked right out of the box, without an Windows XP reinstall? Then why was it that with the first motherboard, the NIC didn't work out of the box, and did do an XP reinstall?
You disproved your own hypothesis that the network problems were a bad ethernet controller on the motherboard with the PCI ethernet controller(that and other users of the board confirmed it was acting exactly like it was supposed to without drivers).
And one of the few things I'm DAMN sure of is that you didn't have a completely non-functional PCI bus.
Therefore, it was a software issue.
It's still fresh.I know that had I listened and just reinstalled the XP, the issue would've likely gone away, and wouldn't have had my head been bitten off, but that's all in the past and I have a new motherboard (which everything works flawlessly) and could everyone just stop freakin' reminding me about the whole bloody thing?
Can't we just put this in the past or am I so doomed as to never have a day go by where someone doesn't remind me about it? Yes I admit I don't know everything and yes, I made several mistakes, so, there you have it.
Soon you'll do something else, and we'll harass you about that.

[img]http://img.photobucket.com/albums/v253/squall_leonhart69r/Final_Fantasy_8/squall_sig1.gif[/img]
[url=http://vba-m.com/]VBA-M Forum[/url], [url=http://www.ngohq.com]NGOHQ[/url]
[url=http://vba-m.com/]VBA-M Forum[/url], [url=http://www.ngohq.com]NGOHQ[/url]
-
- Buzzkill Gil
- Posts: 4295
- Joined: Wed Jan 12, 2005 7:14 pm
I refuse to answer on the grounds that it may incriminate me.Squall_Leonhart wrote:Your trying to find out if he'll snap and commit forum suicide, aren't youGil_Hamilton wrote:As I said... without any way whatsoever of finding out what the hell you were doing, my best is that the new motherboard is more closely related to the old one.neo_bahamut1985 wrote: Then someone needs to do some explaining. Why is it that when I got motherboard B, the NIC worked right out of the box, without an Windows XP reinstall? Then why was it that with the first motherboard, the NIC didn't work out of the box, and did do an XP reinstall?
You disproved your own hypothesis that the network problems were a bad ethernet controller on the motherboard with the PCI ethernet controller(that and other users of the board confirmed it was acting exactly like it was supposed to without drivers).
And one of the few things I'm DAMN sure of is that you didn't have a completely non-functional PCI bus.
Therefore, it was a software issue.
It's still fresh.I know that had I listened and just reinstalled the XP, the issue would've likely gone away, and wouldn't have had my head been bitten off, but that's all in the past and I have a new motherboard (which everything works flawlessly) and could everyone just stop freakin' reminding me about the whole bloody thing?
Can't we just put this in the past or am I so doomed as to never have a day go by where someone doesn't remind me about it? Yes I admit I don't know everything and yes, I made several mistakes, so, there you have it.
Soon you'll do something else, and we'll harass you about that.
-
- ZSNES Shake Shake Prinny
- Posts: 5632
- Joined: Wed Jul 28, 2004 4:15 pm
- Location: PAL50, dood !
The 5th is dead. Choose another character.
皆黙って俺について来い!!
Pantheon: Gideon Zhi | CaitSith2 | Nach | kode54
Code: Select all
<jmr> bsnes has the most accurate wiki page but it takes forever to load (or something)