ETax847 Posted February 23, 2013 Report Share Posted February 23, 2013 If my system doesn't crash, I'm waiting 5 mins at least Quote Link to comment Share on other sites More sharing options...
ETax847 Posted February 23, 2013 Author Report Share Posted February 23, 2013 On top of that, I still am not able to open 3 returns at once without the program crashing Quote Link to comment Share on other sites More sharing options...
gfizer Posted February 23, 2013 Report Share Posted February 23, 2013 Printing time is good now but wait time on opening a return is still long. I can't have two returns open at once at this point due to "low resources." Quote Link to comment Share on other sites More sharing options...
ILLMAS Posted February 23, 2013 Report Share Posted February 23, 2013 Low resource, it's time to upgrade the memory on your PC or you have too many programs open at the same time, ATX2012 is a memory hog. ATX2012 requires a mininum of 2GB, but you can go with 8 or 16BG that would be better. Quote Link to comment Share on other sites More sharing options...
Lee B Posted February 23, 2013 Report Share Posted February 23, 2013 ATX has been posting that the software has in some cases been incorrectly responding to false low resource signals, when you try to open more than one return. This may be on their list to fix in 12.10 ??? Quote Link to comment Share on other sites More sharing options...
SFA Posted February 23, 2013 Report Share Posted February 23, 2013 Every time that I open a return, I go to the M&M drawer. I'm going to get fat waiting for returns to open! 2 Quote Link to comment Share on other sites More sharing options...
ljwalters Posted February 24, 2013 Report Share Posted February 24, 2013 It takes a while for the print selection to load but the actual printing is fine. average 5 minutes to open return some times as long as 7 minutes. I see no reason to open multiple returns that can get you in trouble. I never have more than one return open on my desk either. I have resorted to putting small throw blanket over my desk if I'm working on a large return and someone comes in with a small addition to their return. Quote Link to comment Share on other sites More sharing options...
Janitor Bob Posted February 24, 2013 Report Share Posted February 24, 2013 I just updated from 12.7 to 12.9 due to the need to e-file 4852. I was hoping that maybe the crash/slow opening would improve with 10.9....nope. I knew that 2 gig of RAM was minimum, so I doubled to 4 gig....All I found was that the more RAM you have, the more RAM Loader.exe uses. 1 Quote Link to comment Share on other sites More sharing options...
Lee B Posted February 24, 2013 Report Share Posted February 24, 2013 I'm using an older XP SP3 with only 2 Gig of RAM as a standalone. I waited until after 12.9, before I downloaded the program for the first time because, since I'm a monthly writeup, payroll, & business tax practice, I don't normally start preparing tax returns until about the 20th of February. I can truthfully say that my program opening time is only a bit slower than last year. The client rollover has been fine with one exception. Opening a return for the first time takes about 4 times longer than last year. Then I save the return. When I reopen the return, it takes maybe 10 to 15 seconds longer than last year. When I print, the loading of the print manager takes 2 or 3 times longer than last year, but the actual printing is happening just as fast as the printer can go. I attribute my lack of problems to having a very clean system, minimal stuff running in the background, plus in past years I did not customize anything so my rollovers are very clean. I think anyone who who has been struggling with this program for weeks has accumulated corrupted program files, corrupted forms, and corrupted client files. If you have uninstalled and reinstalled, doing the uninstall through Windows can leave a lot of crud behind waiting to mess up your reinstallation. There have been several posters that have used third party uninstallers so that they can get the cleanest uninstall possible, and as a result had successful reinstalls. I am not saying this program is running well and I am not saying the program doesn't have a lot of bugs. What I am saying is that the program in the right environment is useable, just somewhat slower than last year. My comments only applies to standalone XP systems since that is what I am running. There are a number of posters on the ATX Board running similar sytems to mine with similar results. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.