Error installing VMS from hobbyist CD

Hi Bruce.. Interesting I've just seen your recent post after logged in Forum. If I'm not logged to forum I could see only the post from "March 20 2012 05:04"
Good that you were able to reproduce the problem <img src='../images/smiley/wink.gif' alt='smiley'>

Hey Bruce,

Great news! Fingers crossed it's not too difficult to trace the source.

Steve

< class='quote'>[b:]Bruce Claremont wrote:[/b:]
I have managed to recreate the disk corruption problem using the above scenario. We are now working on isolating the problem's source.

We are having a devil of a time consistently recreating the problem for analysis. The effort continues.

Did any of you have the Charon idle loop enabled when you encountered the problem?

This problem appears to affect disk images of 4GB and larger. This would imply a problem converting 64-bit pointers under 32-bit Windows. We are pursuing this line of reasoning in trying to debug the problem.

For those experiencing this problem, I recommend testing with disk images smaller than 4GB.

< class='quote'>[b:]Bruce Claremont wrote:[/b:]
We are having a devil of a time consistently recreating the problem for analysis. The effort continues.

Did any of you have the Charon idle loop enabled when you encountered the problem?

Hey Bruce,

Yes, I had the Charon idle loop enabled.

Best wishes

Steve

We have posted a fix for FreeAXP-32. You can download FreeAXP 2.1.2.422 at this link: www.migrationspecialties.com/FreeAXP.html#Kits

As we recently hypothesized, the problem was a 32/64 bit issue. Calculation of the offset into a disk to write data is done using a 64-bit variable. Under 32-bit Windows, only the low 32-bits of the result was being saved. This error would impact disks larger than 2GB. The problem only exists under 32-bit Windows. 64-bit systems are unaffected.

If you are using FreeAXP on a 32-bit host system, we recommend updating to FreeAXP 422 immediately. Be advised this is an interim release. We have been testing it for a week without encountering any problems. It has not been through our full Q/A suite.

If you are using FreeAXP on a 64-bit host system, there is no need to apply this update.

For our part, we will be adding some larger disks to our 32-bit test beds to ensure this problem does not re-occur. We extend our thanks to everyone in the forum that contributed to tracking this problem down.