Poxnor
Members-
Content count
52 -
Joined
-
Last visited
Never
Community Reputation
0 NeutralAbout Poxnor
-
Rank
journeyman
-
<nod> I tried Turbo as well. It works quite beautifully. The reason I chose CPU Killer over Turbo was because CPU Killer has a command-line launcher (ie. you can start Warcraft II and CPU Killer simultaneously from a single shortcut). Best of luck!
-
I don't know how much help this will be, but I thought I'd post it for you anyway: I've never personally been able to get Warcraft II working properly under Windows XP. But, because I have 98SE on the same machine, I run it there... Instead of Mo'slo, I use CPU Killer (because Mo'slo wouldn't actually slow down my computer -- it was too fast...anyone with this problem should try CPU Killer). That's how I'm playing Warcraft II... Not sure how relevant this is for you though (ie. whether or not you have a 98SE boot).
-
That sounds like a good rule of thumb Thanks!
-
Hehe, way to go I read about this patch a little while ago on EidosGames.com. Thank you for your effort in helping to make FFVII work on XP. If soundfonts could work well for FFVII under XP, the game would be at 'perfect' level.
-
Oh, okay Thanks for your replies. Since it isn't openly available yet (and still has issues as you mentioned), I think I'll wait until the final version is out before I put it on this machine. --Poxnor the happy
-
Hello, I was curious -- is Windows XP Service Pack 1 Beta available for download anywhere? If so, where? Thanks for your help --Poxnor
-
Hey McBane, Not a stupid question at all, so no worries. Unless you upgraded from another version of Windows (as in, directly installed Windows XP over Windows 98/ME/2k/etc), the only way to uninstall Windows XP that I know of is to format your drive (using a boot disk could make this easier). Be sure to back up all of your important documents and programs before doing this, if formatting is the only option available to you. If anyone knows a better way of uninstalling Windows XP, I'd be most grateful to learn it as well --Poxnor
-
Thank you for your reply Sorry I took so long to reply -- I've been away for a while. Do you know where I would be able to report the problem with the hotfix? I don't get a nice little dialogue box asking me if I want to submit an error report when I reboot after the blue-screen. Thanks for your help! --Poxnor
-
Heyo guys, I figured out the solution to one of my problems -- the Kazaa crash. I simply installed KazaaLite in place of Kazaa, after uninstalling Kazaa then running Ad-aware to remove those foul adware thingies. Has anyone thought of anything about the hotfix-invoked crash? Thanks guys
-
Find a system slowdown utility, would be my recommendation. I know I use one called "Turbo," but I can't remember where I found it. Try looking around the net. They are pretty easy to find. The thing I like about Turbo is that it works, even on faster computers. A lot of the others have either difficulties on faster computers, or you have to pay to get the product that slows down fast computers.
-
Hello guys, I am running Windows XP on my system, and all is going more-or-less well, except for two "problem spots" if you will. There are two things that consistently cause crashes on my system. I was hoping that maybe someone may be able to help pinpoint a cause or solution to either of these problems I've included my system specs at the bottom of this message. ----------------------------------- Problem 1: The Kazaa-Explorer Crash ----------------------------------- Problem 1 is as follows: Whenever I am running Kazaa, regardless of whether the window is opened, minimized, or even iconized by the clock in my task bar, problems ensue. If I so much as type a single letter of text in an open explorer window (ie. when I type in a web address to go to, or even if I type anything in the address field on my taskbar), the explorer window immediately crashes. I tried installing the Windows Update application compatibility patch which promised to resolve problems with Kazaa, but to no avail. If anyone has experience similar problems, and has any idea how to deal with it, your time for a response would be greatly appreciated (Thankfully, this problem isn't major, because I can always just close Kazaa when I want to type something in an explorer window, but that can be a pain, and sometimes I forget...I ran Windows 2000 Professional for a while, and I never had any problems of this sort with Kazaa). ------------------------------ Problem 2: The Patch From Heck ------------------------------ Alright, the second concern I am facing has to do with a patch released a while ago on Windows Update. It is the hotfix that supposedly resolves the "Your system has recovered from a serious error" message on reboot (From hereon, I'll just refer to it as "the patch") Problem is, that patch and my nVidia detonator driver do not seem to get along. (I know that sounds stupid, but it seems that those two entities hate each other or something, hehe). Here goes: When the patch first came out, I was running Det 23.11. I installed that little patch, rebooted, and everything seemed alright. That was, until the first time I tried to play any of my games (Worms World Party, Final Fantasy VIII, etc). I would get an immediate reboot as soon as the game started (as in, right after I clicked on the icon to start it). Figuring this was a blue-screen error, I turned off the auto-reboot option, and sure enough, a blue screen error it was. I apologize, but I did not have the sense to write it down. If anyone needs to know what it is, just post a message for me, and I'll replicate the problem and write it down this time. So, I uninstalled the patch, and everything worked just fine again. Then, the current dets (28.32) came out. So, I installed those dets, and decided, "Hey, let's give the patch a try again" So, I installed the patch again; but this time, the results were even worse. I'd get a blue screen right at WinXP startup (at about the point where the black screen with the blue scrolly thing disappears and the logon screen would appear). So, I went into safe mode, and decided to try a little experiment. In safe mode, I uninstalled my dets, and set my video driver to be just the default driver that comes with Windows XP. I rebooted, and everything worked fine. So, in the end, I wound up uninstalling the patch and reinstalling my 28.32 det, cause the standard Windows driver is icky, hehe. I was just wondering if anyone had experienced similar problems, or if the knew a solution. Thank you very much for helping me look into these problems. Your time is greatly appreciated ------------ System Specs ------------ Athlon 1.4 GHz, on Asus A7M266 256 Meg DDR Ram Asus GeForce 3 Ti500 (w/TV out) Soundblaster Live! 5.1 Dolby Digital Pioneer DVD Rom Plextor Plexwriter CD-Writer Panasonic E70 monitor If anyone needs any more information, please do not hesitate to ask for it. As I've said, and I truly mean it, your effort (in even reading through this entire question, hehe) is something that I am very thankful for --Poxnor
-
Sorry to say, but I'm quite certain that there is no solution to this, at least yet. Myself and several other people were originally involved in an attempt to get FF7 running under Win2k, and unfortunately, this was as good as it got under 2000 as well (everything but the chocobo races). We also made a valiant, but seemingly fruitless attempt on WinXP with the same results. Personally, I wouldn't use my time trying to make it run under either of these OSes until a revalataion from a higher power comes (read: a patch from either Eidos or Microsoft, depending on what gets patched -- if anything does in the end). Sorry to say
-
Hmm, I know that my situation may not entirely apply, but here goes: I also own an A7M266, and I have an SBLive!5.1. I had a problem very similar to your under Windows 2000. I tried everything from PCI Latency fixes, to different custom-made driver sets by 3rd parties, to moving which slot it was in. In the end, though, the solution I found that worked was much, much simpler. I opened up my volume control, and set the Wave, Midi, CD (etc) playback volumes to 50%. I then set the master volume control to about 20%. Finally, I cranked my speakers This worked beautifully, hehe. It was actually a fellow from a little hole-in-the-wall computer shop that explained to me that many of the Creative soundcards don't have the highest-quality audio decoders on them (regardless of what they advertise), and as such, if they are sent a really high amplitude signal (in other words, a really loud thing to decode), they wind up mucking it up and decoding it into static and empty noise (that results in skips). So, when I moved up to Windows XP, I immediately did the same thing (50% on my Wave, Midi, CD, etc. And with XP, I found I could actually bring my master up to around 50% without problems too). And I haven't had any problems. Now, I realize that I'm using a Live!5.1 and you're using an Audigy, so the problem and solution may not be exactly the same. But I figure, knowing Creative, they'd leave a mucky problem like in their product line from one generation to the next. So perhaps it would be worth a try to just turn down the Windows volume control settings a crank your speakers Tell me how it goes -- Poxnor
-
Personally, I would recommend SoundForge for your needs. It may be a little more than what you're looking for... But you can play and edit mp3 files. You can rip from CD to mp3. You can convert all sorts of file types. And it's all standard Windows interface. Again, it may be a little more than what you expect. But give their free trial a try. http://www.soundforge.com , I believe
-
Heyo, Though I've never experienced this myself, I've heard something to the effect that FF7 and the Ge2 don't get along after a certain detonator driver (21.81, or 12.41? I don't really remember). I'd look up the information, but unfortunately, I have to run... It's at www.eidosgames.com --> Forums --> Final Fantasy VII Read through the many posts regarding GeFs and FF7. Most have to deal with people not being able to get Hardware Accel to work for them (which I thought DirectX 8.1 solved practically single-handedly <shrug>), but I remember seeing some other stuff as well. Good luck --Poxnor