HARD Error When Running a ISV Update
Posted on 2007-12-04
We have a pharmacy which runs a DOS-based program on Windows Server 2003. When they try to run their monthly updates, they get a 'HARD' BSod error. I've spent hours trawling through MS and other documentation and found a solution that should have worked. It involves enabling 8.3 file name creation on the drive. To do this, you edit the registry and set the registry key 'Disable8dot3Creation' (or similar) to '0'.
This didn't work and they had the issue again this month. I'm at a loss as the above solution was the only one I was able to find.