cluberti Posted May 7, 2006 Share Posted May 7, 2006 I thought about that as soon as I posted, but I figured I had a 50/50 chance .Sorry you're having trouble with the .iso - I personally use CDRWin to burn .iso's if I'm not using cdrecord, and I've never tried nero, isobuster, et. al as I don't burn many CDs, and find CDRWin and cdrecord to be more cli-friendly . Link to comment Share on other sites More sharing options...
std73 Posted May 10, 2006 Author Share Posted May 10, 2006 It was not the hardware. T42 has an ATI display controllerThe problem is the driver for the ATI display controller. If the driver comes up, it allocates a block of memory.The right way is a BIOS call for this job. It gives a memory area and protects them that no one can use this. Bootix use this technology to protect the memory for the BMA client configuration.The ATI display driver doesn’t use the BIOS. It uses a fixed area and it doesn't care if the memory is protected. It overwrites our protected memory and the interrupt handler that protects the memory is hanging.There is a specific Property within Bootix to prevent this. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now