Hooch provides 14 days of support with your purchase... make him work for his money! 
1 - 19 of 19 Posts
To be fair I bought the disk Hooch ages ago, but have only just got round to using it and he did very kindly send me the link to the "ptv-mfstools2-large-disk" iso anyway.
It could be a bad burn of the CD but that's prolly unlikely. Assuming your 1TB disc is a SATA, how are you attaching it to the motherboard in your PC - is it direct onto the mobo or is it via an IDE-to-SATA converter? If the latter is it one that is known to work or is it a cheap Hong Kong Special?
.
The 1TB is connected directly into the MotherBoard. I do have an IDE2SATA connector which I will use when it's ready to put into the TiVo, but I'm not using it as yet. The IDE2SATA connector that I have bought for that is this one
It could be a bad burn of the CD but that's prolly unlikely. Assuming your 1TB disc is a SATA, how are you attaching it to the motherboard in your PC - is it direct onto the mobo or is it via an IDE-to-SATA converter? If the latter is it one that is known to work or is it a cheap Hong Kong Special?
.
The Startech will be fine (I use it myself).
Ok you need to go back to basics to try and localise the source of the error:
- does the disc show in the BIOS screen and/or the boot sequence?
- (as Staffie said..) does the CD boot when the disc is not connected?
- run the disc manufacturer's diagnostics to check for any SMART errors on the disc (I sometimes get them with brand new discs so just because it's new don't think it isn't broken )
- can you try it on a different socket? (are hda & hdb IDE or SATA ports on your mobo?)
It may be that you have to use the IDE2SATA connector and plug it in to an IDE port (e.g. hdb) - I had to do this since the mfstools disc doesn't support all sata controllers.
Ok you need to go back to basics to try and localise the source of the error:
- does the disc show in the BIOS screen and/or the boot sequence?
- (as Staffie said..) does the CD boot when the disc is not connected?
- run the disc manufacturer's diagnostics to check for any SMART errors on the disc (I sometimes get them with brand new discs so just because it's new don't think it isn't broken
)- can you try it on a different socket? (are hda & hdb IDE or SATA ports on your mobo?)
It may be that you have to use the IDE2SATA connector and plug it in to an IDE port (e.g. hdb) - I had to do this since the mfstools disc doesn't support all sata controllers.
What's the chipset on that Startech?The Startech will be fine (I use it myself).
Ok you need to go back to basics to try and localise the source of the error:
- does the disc show in the BIOS screen and/or the boot sequence?
- (as Staffie said..) does the CD boot when the disc is not connected?
- run the disc manufacturer's diagnostics to check for any SMART errors on the disc (I sometimes get them with brand new discs so just because it's new don't think it isn't broken
- can you try it on a different socket? (are hda & hdb IDE or SATA ports on your mobo?)
It may be that you have to use the IDE2SATA connector and plug it in to an IDE port (e.g. hdb) - I had to do this since the mfstools disc doesn't support all sata controllers.
Thanks to another bank holiday I am having another look at this problem.
I have connected my Samsung 1TB SATA drive Then using this LBA48 image I boot up.
The drive seems to be recognised OK as in attached jpg. It is the only HDD in the PC.
But after that nothing happens, just the blinking prompt. I've tried swapping to the Hooch 1.01 CD at this point but no luck.
I have connected my Samsung 1TB SATA drive Then using this LBA48 image I boot up.
The drive seems to be recognised OK as in attached jpg. It is the only HDD in the PC.
But after that nothing happens, just the blinking prompt. I've tried swapping to the Hooch 1.01 CD at this point but no luck.
Attachments
few more experiments.
I get a similar result if I boot using my usual PC HDD, that is it recognises the HDD and then stops.
if I boot without any HDD however then it gets a bit further - to a linux prompt. But I am then unable to eject the LBA48 disc. So that's not much use.
I get a similar result if I boot using my usual PC HDD, that is it recognises the HDD and then stops.
if I boot without any HDD however then it gets a bit further - to a linux prompt. But I am then unable to eject the LBA48 disc. So that's not much use.
Not yet although I will try that.
I was sort of assuming that since the known working HDD from my PC shows exactly the same symptoms then it probably wasn't the new HDD that was the problem.
I'll check out Samsung Estool. (Probably tomorrow, family to visit today
)You're probably right but I've learnt the hard way to never make any assumptions where women or computers are concerned
1 - 19 of 19 Posts
