1
Ultra Hal 7.0 / UltraHal 6.2 continually crashing
« on: April 21, 2009, 08:40:21 am »
Good morning all
Art and Bill: Thank you for your insights. I DID have NOD 32 on when I re-downloaded Hal. I will throw that download out, restart with all start up files disabled and download Hal once more.
Art, your analysis of the log files I sent is GREATLY appreciated![8D]. No telling how long it would have taken me to tumble to the observations you made (although I'm confident I would have gotten there eventually[:I])
Explanation
NTFS could not write data to the transaction log. This could affect the ability of NTFS to stop or roll back the operations for which the transaction data could not be written. NTFS could not write data because of one or more of the following reasons:
1. I/O requests issued by the file system to the disk subsystem might not have been completed successfully.
Your analysis started me thinking: My system incorporates both EIDE and SATA hard drives (I hate to not use ANY viable hardware- sort of a computer pack-rat one might say). Windows is installed on an EIDE drive which has a slower transfer rate than the SATA drives do. What I wonder is if I were to prep a partition on the SATA drive and install Windows XP there (sort of a dual boot XP-XP), Might having the O/S on the faster drive help overcome the issue described by the link you referred me to? What are your thoughts on this idea? Granted, it is a bit extreme, but I will get UltraHal working on my system reliably and that is all there is to it. Even if I have to go so far as to reformat every one of the three internal drives (2 EIDE and 1 SATA) my system uses! Unfortunately, my ASUS M/B does not give me a choice as to whether I want to use an EDIE or a SATA drive as my Primary. A limitation of using older technology, cheap b/tard that I have to be1
If any other forum members would like to share you thoughts on this issue, please feel free to chime in!
Once again, gentlemen, my deep gratitude for your support with this issue!
Doc
Art and Bill: Thank you for your insights. I DID have NOD 32 on when I re-downloaded Hal. I will throw that download out, restart with all start up files disabled and download Hal once more.
Art, your analysis of the log files I sent is GREATLY appreciated![8D]. No telling how long it would have taken me to tumble to the observations you made (although I'm confident I would have gotten there eventually[:I])
Explanation
NTFS could not write data to the transaction log. This could affect the ability of NTFS to stop or roll back the operations for which the transaction data could not be written. NTFS could not write data because of one or more of the following reasons:
1. I/O requests issued by the file system to the disk subsystem might not have been completed successfully.
Your analysis started me thinking: My system incorporates both EIDE and SATA hard drives (I hate to not use ANY viable hardware- sort of a computer pack-rat one might say). Windows is installed on an EIDE drive which has a slower transfer rate than the SATA drives do. What I wonder is if I were to prep a partition on the SATA drive and install Windows XP there (sort of a dual boot XP-XP), Might having the O/S on the faster drive help overcome the issue described by the link you referred me to? What are your thoughts on this idea? Granted, it is a bit extreme, but I will get UltraHal working on my system reliably and that is all there is to it. Even if I have to go so far as to reformat every one of the three internal drives (2 EIDE and 1 SATA) my system uses! Unfortunately, my ASUS M/B does not give me a choice as to whether I want to use an EDIE or a SATA drive as my Primary. A limitation of using older technology, cheap b/tard that I have to be1
If any other forum members would like to share you thoughts on this issue, please feel free to chime in!
Once again, gentlemen, my deep gratitude for your support with this issue!
Doc