PicoBot

Member
  • Content count

    4
  • Joined

  • Last visited

Community Reputation

0 Neutral

About PicoBot

Profile Information

  • OS
    XP Pro x86
  • Country
  1. Hi, I am just dropping in to report that the installation of XP from an ISO, where both the mass storage drivers needed by the mobo and firadisk have been integrated using nlite, works fine. I built a XP ISO with drivers for all types of Intels ICH7(x) to ICH10(x) controller ( both raid and ahci drivers ), NVidias Nforce7 chipset ( raid and ahci ) and firadisk itself. Then I used the following configuration ( winsetup.lst ) for grub4dos: title First part of Windows XP setup from ISO map --mem (md)0x800+4 (99) map /XP.iso (0xff) checkrange 0x80 read 0x8280 && map (hd0) (hd1) checkrange 0x80 read 0x8280 && map (hd1) (hd0) map --hook write (99) [FiraDisk]\nStartOptions=cdrom,vmem=find:/XP.iso;\n\0 chainloader (0xff) title Second part of XP setup from ISO / Boot first internal hard drive map --mem (md)0x800+4 (99) checkrange 0x80 read 0x8280 && map (hd0) (hd1) checkrange 0x80 read 0x8280 && map (hd1) (hd0) map --hook write (99) [FiraDisk]\nStartOptions=cdrom,vmem=find:/XP.iso;\n\0 chainloader (hd0)+1 The HDD for the installation was NOT connected via USB, because my mobo ( GA-P35DS3R rev. 1.0 ) only boots from USB in 1.1 mode and "Plops" USB driver did not work for me. Instead, the installation HDD was connected to the 4. S-ATA Port of the ICH9R, and the target HDD was on the 1. S-ATA port. Then I booted the installation HDD via the boot menu of the bios, which explains the mappings I needed in the winsetup.lst . I never installed a Windows XP so fast, even it could have been faster, since the installation HDD was only a 2,5" drive with 5400 rpm, which normally belongs into an external USB enclosure. Of course this method should work the same way if the installation HDD would have been booted through USB, but I did not test this since it would have been painfully slow with my mobo. C.U. Picobot
  2. Well, forcing the drive to download the CC46 firmware without any further investigation of course would not be wise, especially since the drive works without any problems. To find out the reason for the update failure, the solution would be to build a serial cable and to check the version of the firmware modules via serial communication. And this IMHO is not worth the time and effort at all, so the drive will continue to work with CC31. C.U. PicoBot
  3. Hi jaclaz, thanks for the link to the older firmware version. I was also able to find the CC3D version: http://www.seagate.com/staticfiles/support/downloads/firmware/Barracuda12-ALL-CC3D.iso Nevertheless, both versions are not willing / able to update this specific drive. The only progress I made is that I have written down the exact error messages: "Modell matched, no firmware match, will not download firmware" and "Modell matched but firmware version is not compatible" I am beginning to believe that there really is a small difference in the hardware and therefore the newer firmwares must not be used with this drive. So my hope is, that the newer firmware is not such important and there are no "hidden" bugs like there where in the 7200.11 firmware C.U. PicoBot
  4. Hi everybody, two days ago a friend of mine informed me that the CC46 firmware update for most of the 7200.12 drives is available at seagate's website. I downloaded and burned the CD ISO image and was able to update six of my seven 7200.12 drives. These drives are five ST31000528AS, originally equipped with CC34 and the CC37 firmwares, and one ST3500418AS, which originally had the CC38 firmware. With these six drives everything went fine, no problems at all. But one of my drives, a ST3500410AS, which currently works with the CC31 firmware, can't be updated at all. The updater reports that the updater is ok for this modell, but the firmware the drive has now ( CC31 ) and the new firmware ( CC46 ) are not "compatible" ( sorry, i can't remember the exact error report now ) and therefore rejects to update this drive. Is anybody of you aware of this problem and has informations about the reason for this behavior ? I can imagine three possible reasons: 1. This drive is one of the first exemplars of this drive, which has been sold, and is a little bit different in hardware. That would explain, why the CC46 firmware must not be used with the drive. 2. The firmware updater from seagate simply is not aware that there are drives with the firmware version CC31 and therefore "thinks" that the CC46 should better not be used with my drive 3. The version jump from CC31 to CC46 is too big and some of the internal data structures have been changed. Perhaps an "intermediate" update from CC31 to CC34 and then a second update from CC34 to CC46 might work, but i can't find any older firmware updates for this drive. Is anybody of you able to tell me if and which of my guesses is correct ? Thx for reading, PicoBot