Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 

hairy coo

  • Content count

  • Donations

  • Joined

  • Last visited

Community Reputation

0 Neutral

About hairy coo

  1. Unable to uninstall nlite 1.4.6

    No you cant uninstall that way-vital remnants will be left over. Suggest you reinstall the same over the top of the existing install-then check again as there definitely should be an uninstaller present in the Programs/nLite folder. In any case,go HERE and download the free-Revo Uninstaller,excellent and should show everything.
  2. A conflict with nLite

    If running Threatfire, you may well receive a fatal error message, when integrating drivers into nLite ,making it impossible to proceed. The message is the dreaded "nLite has encountered a problem and needs to close" etc. A conflict seems to exist between Threatfire and nLite. Just temporarily suspending Threatfire will solve the problem, no need to uninstall. I noticed from another thread that other security apps-anti-virus and firewalls may also conflict. Good Luck Hairy edit; Threatfire is a heuristic HIPS behaviour blocker which focuses on detecting and blocking generic malicious behavior and events as they happen. Some action happening during the nLite process is apparently being misinterpreted. .
  3. Integration of Intel's SATA AHCI and RAID drivers

    As per my previous posts,I was currently unable to load RAID or any type of drivers using nLite. As before I was completely successful-I searched for a conflict and the only extra app. installed since success, was Threatfire,an anti spyware and malware tool. Since disabling Threatfire,everything is back to normal. I will post a new thread in case this may help someone else.
  4. Integration of Intel's SATA AHCI and RAID drivers

    Fernando, You seem to insist in dragging this out quite uneccessarily,as I already said I would solve the problem myself. Regrettably your inflammatory reply adds nothing of value, but seems to illustrate your approach when an issue occurs outside your field of knowledge. The other person is just not telling the truth and of course must also be completely wrong -quite simple-problem solved-a winning formula If you take the trouble to really read posts instead of rushing in with your dogmatic answers,you will note that I was careful to give examples that nLite does work for me and has done so. I am in fact running on a perfect nLited XPsp3 -as I mentioned, ONLY with the RAID drivers did I have problems and ONLY with XP2. I also inferred it could be a Windows issue,as a Windows error message appeared If I could give you some well meant advice Instead of taking a problem to which you dont have an answer personally -may I respectfully suggest that in future you would be better served by listening and then deciding if in fact you have anything to offer. If its outside your knowledge ,just admit it instead of wasting everyones time. Everyone has their limitations!! Good luck to you in your self appointed role of playing the "expert"-some more friendly advice-try changing your attitude for better results. Also try to be accurate in stating what the other person has in fact said,rather than misquoting them- in order to achieve some credibility. best regards hairy
  5. Integration of Intel's SATA AHCI and RAID drivers

    Fernando Your replies are appreciated,but regrettably we are going round in ever diminishing circles without achieving anything I keep saying all my steps are correct (its really not nuclear physics after all), including the drivers choosen -and my copy of XP is perfect,but you persist in questioning all of this. I was asking for some new answer and was quite happy to acknowledge some unique problem which someone may have also experienced, but obviously all this must be unknown. Anyway,thanks for your effort-I will solve the problem-pointless going over old ground yet again.
  6. Integration of Intel's SATA AHCI and RAID drivers

    Fernando .Not obvious at all! Your textmode drivers were used and the correct controller, ICH9r RAID,was chosen. As said before-all the usual stuff was double checked and carried out correctly,including that Textmode was enabled, Have not tested this,but think XP F6 was unsuccessful because existing drivers ie iastor(For use with AHCI) were already present-this was the case when using Shadow protect F6 failed,which announced the fact. Ahem-the only one not showing is the RAID controller-as I'm again using AHCI mode the Intel ICH 9r/DO/DH/ SATA ACHI controlller is present. If the SCSI and RAID Controllers were present-I obviously wouldnt have any problems ,after all. OK ,ignoring any other problems which are a different matter -all could be solved if nLite would work for me and as I said,it should function independently of outside conflicts by and large. I dont understand either and was hoping this problem may have been encountered by someone else-but it seems not.. Previously have used nLite successfully on many occasions installing Intel INF drivers,but not the RAID ones. I am running perfectly on a slipstreamed XPsp3 created by nLite 1.45 using the same master XP2 disk and NEVER had any problems until now. Did further tests-used a previous version of nLite-still no good.My version in use is 1.46. However using Win 2000 instead of XP2-success!! My XPsp2 disk is a perfect, clean,legal,faultless validated version, as I said, used many times before for slipstreaming. So there is the fault location. FOR ME; nLite and Windows itself,as a Windows fault message appears- will not allow integrating the Intel Raid drivers with XPsp2,but will with Win2000. Will try to activate RAID by installing temporarily the 2000/RAID slipstream on an external disk connected to the jMicron/Gigabyte IDE controller to bypass the Intel controller.
  7. Integration of Intel's SATA AHCI and RAID drivers

    Yes, the original clean XPSP2 and the 100% correct procedure was carried outthroughout. The problem is strange because even if there is some other conflict somewhere to do with enabling RAID,nLite can insulate its own processes ,surely, from any other issues. Have tried every possible method-,using JMicron controller for the C drive prior to installing the RAID drivers on the Intel controller-using a new Windows install using F6-using Shadow Protect F6 etc-all fail. I'm running AHCI mode,which was installed by placing the iastor driver into win32/drivers plus a registry fix,wondering if that may have something to do with it,as iastor is already in place-but it shouldnt affect nLite.. Probably the AHCI driver should have been used. If I cant fix will have to try the Gigabyte/Micron RAID controller unwilllingly Thanks and any further thoughts would be appreciated. edit;have removed the AHCI reg fix and iastor driver and will plod on !!
  8. Integration of Intel's SATA AHCI and RAID drivers

    Fernando, Would appreciate some help regarding the nLite install of the Intel RAID drivers. As far as I'm aware ,all steps necessary for a successful integration have been carried out However, at the finalizing stage of nLite,an error message crops up every time , indicating nLite has to close etc. The whole procedure has been lost at least 6 times because of this- time to stop. The only meaningful part of the very lengthy error report for me was the mention of an "appcompat.text" error. By elimination,I have narrowed the fault down to the integration of the Intel TextMode Raid Drivers,which is all that was slipstreamed,nothing else at all! The addition of the Intel INF drivers does not help either. Textmode is enabled. Have used the latest drivers containing txt.setup.oem. No malware is present. Thanks Hairy edit;My reading of the Intel instructions indicates that a text file containing the following ; "[MassStorageDrivers] "Intel® 82801IR/IO SATA RAID Controller" = OEM [OEMBootFiles] iaStor.inf iaStor.sys iaStor.cat Txtsetup.oem" should be added to the drivers file for unattended installs. Is this at all relevant?.Is it the same as the TxtSetup.OEM File? However, it made no difference in my case.