I have A1 Click Ultra (registered version) installed on a 'generic' PC running XP Pro. Recently when I tried to run the program, it would hang shortly after starting, and a window would appear stating "Exception Processing Message c0000013 Parameters 75b6bf7c 4 75b6bf7c 75b6bf7c" The window with that message is then frozen to the screen and it can not be closed in the normal manner. I have to abort the program with Windows Task Manager to get rid of the message window and the A1 program start window.

I have uninstalled, rebooted, and re-installed A1, run Reg-Vac numerous times (successfully), and still can not get A1 to load.

I'm reasonably comfortable with using regedit as long as I know what line item(s) to look for to modify or eliminate if this is necessary. I just need a push in the right direction. Any help would be gratefully appreciated.

Thanks in advance. . . Buzz

   The problem would not be in the registry.
   You might try renaming the a1clean.ini file in the A1Click directory to a1clean.inb and see if that works.

Thanks for the reply Ray. I don't see an A1Click.ini file in the directory. There is an A1Click.CNT file, a help file, the application file, and others with various names. I downloaded a fresh copy and installed that. Same results, the program gets as far as the opening logo, and hangs.

   a1clean.ini not a1click.ini
   A1Click makes that file when it starts.  It could be that it did not get started far enough to make it.
   I just remembered a problem like this that some had a few years back.  The problem was a corrupt Java installation.

O.K. Thanks - I'm squared away on the file names now.  8-)

I'll fiddle around with the Java thing and see what happens.

I removed all the Java programs, and still get a lockup.
Additional info on the error window - in the border on top left it says "Windows - No Disk".

Do you have an a1clean.ini file?

No. The program locks up at the same point as before.

O.K., folks, fwiw, I successfully ran the program today, 5 March. I don't know when or how the problem got resolved, but for now we're back in business.

Good.  Thanks for letting us know.