Sign in to follow this  
Guest wyoming

It finally happened to me...

Recommended Posts

First, let me acknowledge that I have no business posting this but, in an effort to make myself feel a little better, I'm going to rant a bit anyway. I encountered the dreaded 1722/1603 error some days ago. I have tried every fix known to man. FSX will not reinstall. After 50+ hours of trying I give up. I will NOT reformat to solve this problem. Accordingly, I am now in the process of trying to remove all vestages of said FSX program and will, without remorse, go back to flying FS2004 only. I'm not looking for help and I'm not looking for sympathy. I've been around too long for that. I'm just PO'd. There. I feel better already. End of rant.Doug

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

Absolutely absurd, and something MS should address regardless of how minor they think it is. I can't think of any reasonable person who could support such nonsense, and to expect an end-user to reformat is even more asinine. I've never had to reformat for any FS software or program, and I wouldn't start now.Despite how good FSX might be for people, it has a lot of problems.

Share this post


Link to post
Share on other sites

>>I've never had to reformat for any FS software or program, and I wouldn't start now.<

Share this post


Link to post
Share on other sites

DougIf your OS is Vista a reformat may still be in your future even after removing FSX. The mskb928080.exe will in most cases resolve the 1722 FSX startup problem but all the Stores also become corrupt.I have found on my new Vista system that the 1722 is not FSX related per se but normally what causes the startup error is based on something else such as a beta Driver. In my case it was Nvida which is still trying to rush to market with Vista drivers that are still not stable for my 8800 GTX SLI's. Because the Drivers for my XP SP2 computer are more stable I have not had any BOD's that effect the Registry and then causes the FSX 1722. Many say that Vista has problems but so do all the Drivers trying to run Vista including Sound cards, Video, Printers, etc. Even utilities like the Norton 360 and PCtools are still trying to fiqure out Vista. My Norton 360 is being updated daily and they still have not fiqured out a complete GoBack reImage of the hard drive like they did for XP.

Share this post


Link to post
Share on other sites

Vista's not the problem Jim. I gave up on that OS many months ago :-). I'm running an XP box which was reformatted and the OS reinstalled 32 days ago. The drivers for both the mobo chipset and attached devices are all tried-and-true - I've been using them for months. Everything on this system is really plain-vanilla. I don't even OC it anymore. Grrrrrr....................I gotta go fly the PMDG 737 now. In all the FSX frenzy I'd forgotten just how much I love that airplane. And the Dreamfleet stuff, and FSNav, and......Doug

Share this post


Link to post
Share on other sites

You reformated the drive your os was on, yes? I'm trying to decided if my development files are at risk if they're on the same drive as fsx, but its the regestry that must be wiped and reinstalled I would think. Please confirm?Bob

Share this post


Link to post
Share on other sites

> Me too :-fume I too am disgusted with the Activation feature in FSX.:-fume is quite an appropriate smiley for the 1722 error.RhettAMD 3700+ (@2585 mhz), eVGA 7800GT 256 (Guru3D 93.71), ASUS A8N-E, PC Power 510 SLI, 2gb Corsair XMS 3-3-3-8 (1T), WD 150 gig 10000rpm Raptor, WD 250gig 7200rpm SATA2, Seagate 120gb 5400 rpm external HD, CoolerMaster Praetorian

Share this post


Link to post
Share on other sites

Hi Bob, it's interesting you (maybe indirectly?) brought up paths. I wonder whether Doug and others who are experiencing this problem, installed FSX in default locations or not? And of course, sorry to hear about 'your' troubles, Doug. 50h solving something which apparently works must be highly frustrating... I went through similar events with 8-month old Nvidia drivers and no updates... Felt like: http://www.youtube.com/watch?v=gJDUS9W9p5Y...related&search=Cheers and kind regards Jaap Some others: http://www.youtube.com/watch?v=DdSZ5GgLcDs...related&search=More Britons:

Share this post


Link to post
Share on other sites

I somehow hadn't heard of this until now. But some quick searching and I see it all over. Wow. That's disgusting. And scary. I sure hope it gets fixed with SP2....maybe ACES has been getting pointers from the 360 team?

Share this post


Link to post
Share on other sites

One other thing to check. I think I remember someone reporting this problem a couple of months ago, and it turned out, that some how DEP got set on the system preventing the fix to work! Check to see if it got turned on in your system and if so try turning it off!EDIT: I found it, but it was the User Access Control (UAL) in Vista, not DEP that caused it. (It was Geofa post when he had the problem) Not sure if this could be an issue in XP too? Have you changed your user rights recently? Like say from administrator to limited user?

Share this post


Link to post
Share on other sites

Doug, I don't know what kind of setup you have but the best is to put FSX on a separate hardrive and that way the reformat is not such a problem. I have had the errors since last October and have not done any reformats.Tony

Share this post


Link to post
Share on other sites

>Doug,>> I don't know what kind of setup you have but the best is>to put FSX on a separate hardrive and that way the reformat is>not such a problem. I have had the errors since last October>and have not done any reformats.>>Tony Wouldn't it still be a problem? I mean, what about the FSX registry entries? They would be on the OS drive and would get wiped by a reformat of the OS drive...Or can FSX rebuild its registry entries in some manner?RhettAMD 3700+ (@2585 mhz), eVGA 7800GT 256 (Guru3D 93.71), ASUS A8N-E, PC Power 510 SLI, 2gb Corsair XMS 3-3-3-8 (1T), WD 150 gig 10000rpm Raptor, WD 250gig 7200rpm SATA2, Seagate 120gb 5400 rpm external HD, CoolerMaster Praetorian

Share this post


Link to post
Share on other sites

> I don't know what kind of setup you have but the best is>to put FSX on a separate hardrive and that way the reformat is>not such a problem. I have had the errors since last October>and have not done any reformats.Well, good thing all software isn't like this! I'd hate to have to have a each piece of software on its own partition.... what a waste.It seems to me the problem is installers are trying to be too "smart" these days. Ironically, I think idea is by making the installers smart enough to take everything on a customer's system into account, you could avoid many of the pitfalls that happened for customers on "unique" systems. But when the process gets too complicated, one blown step and the installer/uninstaller is useless.Why can't installers simply include a "force" over-install option that dumps files, registry entries and registers classes they way installers used to work? It seems absurd to me that remnants of a previous installation should be allowed to stand in your way of an overinstall. FSX is not the only place I've heard of such problems... we actually have dealt with similar (though perhaps not so severe) situations at my job quite often-- for instance, since moving to use InstallShield 12 to produce our installs, we went through period of time where we were having many problems with the installer not replacing files it needed to when trying to update customers. We finally have somewhat hacked the installer in a way that seems to be forcing a complete overinstall for everybody, but it took an incredible amount of time to figure out how to get it to do a "dumb" overinstall. Maybe we just don't know InstallShield 12 well enough yet, but it seems absurd to me that it should be so hard to get the installer to stop thinking so hard about the install process and just dump the files.While I'm on a roll.... anyone else here had the experience of installing Visual Studio 2005 in 20 minutes, but then watched SP1 take over 2 hours to install? (most of it in the "gathering required info" stage. What the heck is it "gathering"? I could run a complete virus scan of my system in that time...) ASX/XG seems to be victim of the same process.... I wanted to move the installation a while back... while uninstalling took about 30 min rather than over 2 hours, it still took many many times longer than installing it in the first place... most of it in the "gathering required info" step). And Sage's ACT is one of many other pieces of software where I've experienced the problem of not being about to re-install because the installer was finding remnants of a previous install... which, of course, it was unable to uninstall (though I've never encountered a situation so bad that I had to reformat... up to now, cleaning out registry entries has eventually done the trick).Anyway, my plea to installer makers out there: stop the madness! There may be shortcomings to having dumb dump-the-data installers, but you have to at least give us that option for the cases that your installers outsmart themselves.

Share this post


Link to post
Share on other sites

Another couple of questions and thoughts... :-) We know winXP and Vista 'self-optimize' around the C drive, do these operating systems also optimize D, E, F, etc? 2nd thought: FSX 'scatters' files all over our C partition; the FSX.cfg is in the OS-user profile, the scenery.cfg is in 'an all users' profile, saved flights are in yet another folder, etc. I wonder to which degree we're calling for havoc (or increased need for support for that matter), if we install away from defaults? Has anybody considered (or tried); instead of installing FSX in 'D', mapping the same HD to its default location in C? This maybe could be an elegant solution to keep the paths but yet still enjoy the benefits of an extra harddrive? Cheers and kind regards Jaap Edited, still can't spell and think logically! :-)

Share this post


Link to post
Share on other sites

No change Tom. I've always been the administrator. As far as UAC in Vista, everyone should turn it off at the first opportunity. I get enough "protection" from the government, I don't need more "protection" from Microsoft :-). Thanks for the input though.Doug

Share this post


Link to post
Share on other sites

You're right Rhett, it's a problem no matter where FSX is installed. I have eight drives on this system but only one Registry - and that's on the drive with the rest of the OS. Format or restore the drive where the OS resides and the current Registry is also obliterated. I have to restore the OS drive back to a base imgage once each quarter for security, and other, reasons so I'm VERY familiar with the problems of managing 2TB of data across eight physical drives.I'm going to wait until the first week in October when the next restore is scheduled and see what's what then. I'll either reinstall FSX after that restore or, if the timing looks right, just wait for SP2 and install the whole thing then.But, as I said earlier, I wonder how Joe Average and his kids are doing. I can't imagine the average computer user running into this problem and having to deal with the non-support from MS. Grrrrrrr............. :-fume Doug

Share this post


Link to post
Share on other sites

I'm sorry this crap is happening to ya...I haven't had the said error myself (yet) but if I did I'm sure I would ERRRRR GRRRRRR AHHHHHHH Q#$$%^$#&$%^#$ all over the place! So that's for you! GRRRRR ACTIVATION GRRRR!!!

Share this post


Link to post
Share on other sites

>But, as I said earlier, I wonder how Joe Average and his kids>are doing. I can't imagine the average computer user running>into this problem and having to deal with the non-support from>MS. Grrrrrrr............. :-fume Doug, it's quite likely that "Joe Average and his kids" aren't having problems. They probably aren't constantly tinkering with things and installing a bazillion bytes of add-ons... :)

Share this post


Link to post
Share on other sites

>While I'm on a roll.... anyone else here had the experience of>installing Visual Studio 2005 in 20 minutes, but then watched>SP1 take over 2 hours to install? (most of it in the>"gathering required info" stage.Yes - been there twice. > What the heck is it "gathering"? I could run a complete virus scan > of my system in that time...)I wish I knew - Visual Studio 2005 seemed to upset a lot of developers when it first came out. I now try and program in Java on my Mac whenever possible, despite spending years using Visual Studio and C++. It's a lot less frustrating.I wish Windows installations were as simple as the Mac as well - you just drag and drop an App folder and that's it. No installer required... I better shut up about Macs before I'm accused of being a member of the cult - my MacBook Pro does seem to run FSX very nicely though! :D

Share this post


Link to post
Share on other sites

I waited until a nice afternoon here to install VS on my work computer, it gave me plenty of time to take a walk on the grounds at work, get a tan, etc.I just assumed that the SP1 install was finding pieces and updating them instead of just overwriting files with new files, to minimize the download size of the service pack. I could see how the hunt and peck method of shuffling bytes would take a good deal longer than "copy file from point a to point b".

Share this post


Link to post
Share on other sites

>I just assumed that the SP1 install was finding pieces and>updating them instead of just overwriting files with new>files, to minimize the download size of the service pack. I>could see how the hunt and peck method of shuffling bytes>would take a good deal longer than "copy file from point a to>point b".I don't buy that... plenty of installers do just that without requiring all afternoon to do so. Well, okay, I buy the idea that that is what is taking so long, but dispute the idea that it *needs* to take that long.EDIT: I'm particularily suspicious that .Net may be the culprit. It seems to be applications that use .Net that I notice the long "gathering info" problem including ASX/XG and Sage's ACT that I mentioned above.

Share this post


Link to post
Share on other sites

>>I just assumed that the SP1 install was finding pieces and>>updating them instead of just overwriting files with new>>files, to minimize the download size of the service pack. I>>could see how the hunt and peck method of shuffling bytes>>would take a good deal longer than "copy file from point a>to>>point b".>>I don't buy that... plenty of installers do just that without>requiring all afternoon to do so. Well, okay, I buy the idea>that that is what is taking so long, but dispute the idea that>it *needs* to take that long.>>EDIT: I'm particularily suspicious that .Net may be the>culprit. It seems to be applications that use .Net that I>notice the long "gathering info" problem including ASX/XG and>Sage's ACT that I mentioned above.I'd certainly be curious to see what the installers are written in. I know some guys who work with WiX, and I'm going to pass this by them to see if they encounter that problem. Nothing that can't be tracked down by some research, I'm sure.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this