Looking for help to cure a RECOVER problem. I've installed V13 on a new machine with Windows XP. Everything went well during install and RESTORE of data from old system. The problem is in the AP module. The first time I tried to RECOVER the system hung-up. I was able to CTRL+ALT+DEL to END TASK. I tried the process again. It worked. All other RECOVER on other modules worked fine. Doing some other troubleshooting, I tried the RECOVER again on AP and it hung again. Long story short, it's intermittant. If I try the process again it will succeed. It's about a 1 in 3 or 1 in 2 chance it will work.
I don't want to proceed with commissioning this machine until I find a solution to this problem. I don't think it is the data as it will RECOVER maybe even 2 times in a row. I don't think it is the hardware, it's working so well on other tests.
Does XP use the AUTOEXEC.BAT and CONFIG.SYS? I saw on another forum that XP uses a CONFIG.NT instead of SYS. What are the suggested parameters for the CONFIG? Are there any other set-up suggestions for XP and Version 13?
Thanks in advance.
Doyle
I don't want to proceed with commissioning this machine until I find a solution to this problem. I don't think it is the data as it will RECOVER maybe even 2 times in a row. I don't think it is the hardware, it's working so well on other tests.
Does XP use the AUTOEXEC.BAT and CONFIG.SYS? I saw on another forum that XP uses a CONFIG.NT instead of SYS. What are the suggested parameters for the CONFIG? Are there any other set-up suggestions for XP and Version 13?
Thanks in advance.
Doyle