VideoHelp Forum




+ Reply to Thread
Results 1 to 2 of 2
  1. Member
    Join Date
    Jan 2006
    Location
    United States
    Search Comp PM
    Recently I got a SYBA SD-SATA-4P PCI card with SIL3114 chupset for my PC, and everything works fine in Win2k with SATA hard drive connected. However, I get "Stop: 0X0000001E(0XC0000005,0XEB0717A6,0X00000000,0X0000 0028) KMODE_EXCEPTION_NOT_HANDLED" just after the Windows 2000 Professional screen while booting when SATA burner is attached. This is on a multi-boot system with Win98SE and WinXP plus Win2k. Both WinXP and Win98SE boot fine with hard drive and SATA burner connected. SIL3114 drivers were installed for all 3 Windows versions before before attaching any SATA drive.

    WinXP required a repair install before it would boot even to the hard drive, and I thought repair install may be the solution for Win2k. However, the same error is given after the first restart during repair install. I then had to restore a recent backup image of C drive to be able to boot to Win98SE or WinXP because it kept trying that repair install restart with no boot menu to select.

    Is Win2k incompatible with SATA adapter cards, or is there a solution for this problem? Another option I considered is to do a limited and separate WinXP install to replace the Win2k install. Would WinXP need to be activated again if a separate install were done, and are there any problems with having 2 separate WinXP installs?
    Quote Quote  
  2. Member
    Join Date
    Jan 2006
    Location
    United States
    Search Comp PM
    I finally figured out what the cause of the problem was when I tried to a Win2k repair install. For some unknown reason the Win2k install disk was seeing the current Win2k installation on a different drive letter than where it was originally installed, and Win2k was probably looking for it on the original drive letter when it was trying to load. I've no idea what may have caused this odd behavior. Also it's odd that WinXP stilll recognized correct drive for Win2k already installed while Win98SE recognized original Win2k install on the different drive just as Win2k Setup did. Go figure!

    Anyway the problem was finally fixed by first deleting some partitions, then recreating them to get Win2k to see its target partition as the correct drive letter, and finally doing a fresh Win2k install. This fixed all Win2k issues, and all SATA drives are now correctly recognized.

    However, WinXP would not boot after that because in multi-boot Windows systems the OSs must be installed from oldest, next to oldest to newest as some may know and others may not know. I then tried a WinXP repair install which would not complete because it asked for the timntr_2k.sys file which couldn't be located. Some google searches revealed that file is part of Acronis, and suggested solution was to install Acronis to get the file which worked for the guy who was seeking it. This is even more strange because Acronis was never installed on the system, and I don't even have the Acronis program. A fresh install of WinXP fixed this problem, and a recent WinXP backup image was restored which resulted in everything back to normal in a short time. It probably wasn't necessary to go into as much detail on the resolution to problems, but maybe it may help someone else who experiences these any of these issues.

    Edit: BTW in the deleting partitions part of the resolution to problems WinXP gave the message "Partition cannot be deleted" when trying to delete the partition that Win2k had been installed on, but use of fdisk in Win98SE removed the partition with no problem. Older OSs do have some surprising usefulness despite what some may think. I don't know how that partition might have been deleted if not for fdisk and Win98SE.
    Last edited by bevills1; 24th Apr 2013 at 21:38.
    Quote Quote  



Similar Threads

Visit our sponsor! Try DVDFab and backup Blu-rays!