Jump to content

geoslake

Member
  • Posts

    7
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    France

About geoslake

Contact Methods

  • Website URL
    http://

geoslake's Achievements

0

Reputation

  1. Thanks for the feedback. Yeah I downloaded the manual, and by default, the bios is set to "pata(ide) mode", that's why you didn't encounter any problem
  2. Hi I will soon upgrade my system, and am worried about the sata thing. Mobo : Gigabyte EP45-DS3L Hd : Hitachi Deskstar P7K500 (Serial ATA-II) It seems south bridge takes care of sata, and it's an Intel® ICH10 IDE is handled by JMicron 368 chip I guess I should integrate Intel drivers anyway but I've read various posts here, and im not sure, as some people get bsod etc... And I'm not planning to use RAID (n/a on this mobo anyway), nor AHCI (as it seems there are only few advantages). So am I wrong if I : - set the HD to IDE mode (or non AHCI or whatever)(is this option available on any mobo/bios btw ?) - plug the HD using sata cable (it can be plugged with sata, but used in IDE mode, right ?)(weird) Or do I really miss something/will face performance loss etc Thanks
  3. yes, this indeed fixed my problem thanks to you
  4. Ok, I had a look at the windows folder after having integrated Ryan 1.0.1 update pack. Seems every file there ends up with something like .TT_ or .SY_ so the last letter is "hidden". But that doesn't happen with those : KSECDD.SYS ntfs.sys Yes, this one (ntfs.sys) has its full extension (.sys i mean) AND is lowercase !! Could this be the cause ?
  5. Please see beginning of my post. No, this is with a fresh cd. I will repeat the procedure and check if it is on the iso, but I'm afraid it's packed as .cab or something... thanks
  6. hi I got this message at the end of the drivers loading (with the blue blackground at the beginning of the install procedure). My cd has sp3 integrated, and I already installed it fine, nlited (services removed etc) and all. BUT this happens after having integrated hte latest ryanvm 1.0.1 update. Is it possible for this to have generated such error, as it was released post to latest nlite version ? Or may it be because I changed something, like, burning speed or so ? I think i followed the guidelines, integrating the ryanvm pack first, then closing nlite. THEN I restart nLite and start the nlightment. thanks
×
×
  • Create New...