PVU

Dude, did someone steal your handle or password? That's a generous post coming from a Win2K guy who isn't into XP. Could it be that fdv has finally broken down (after SP3) and is now using (or getting used to) XP? fdv, did you just buy a new laptop or PC with AHCI SATA? Maybe Vista is starting to make XP look like Windows 2000. Hell, I don't know. This is an amazing post, though. Thanks, Fred.

Very interesting. When I got that laptop, I knew I would format and do my own clean install. So I kept the Dell install up long enough just to understand which drivers I would need. When I tried to install the updated 7.8.0.1012 IMSM, it wouldn't take it and I bummed out - thinking Dell might have used a cheaper ICH8 chipset without SATA support. Then I went into the bios, flipped it to AHCI, and the Dell installed OS picked it up. So I was happy about that and clean installed 2K3 with the integrated drivers while the bios was set to AHCI. One thing about your last issue was that maybe you were using a pre-release/beta version of the IMSM - that may have had something to do with it. But I do know that the latest one should work, so your timing is good now. I don't know if IE7 is really an issue. I'm also not sure about WMP11. Then again, I don't know about your nLite install - there are too many variables. What I like about HFSLIP is that if there's a hotfix integration issue, it bubbles up to the top right away - the WMP11 + SP3 is a good example. If you're having issues like this, the more you can cut out, the better. Getting the drivers right right from the beginning is more important to me than integrating a few additional items that can be easily added later. If you go conservative, you'll get the driver issue behind you. You could go for broke now that you have the latest official driver set, but I would just include SP3. But I would definitely fresh install with the BIOS set to AHCI. If the install doesn't pick up the HDD, you'll know you probably did something wrong as far as integrating drivers with nLite is concerned. If you go the nLite route to integrate the drivers, you should have no problem if you follow Fernando 1's instructions: http://www.msfn.org/board/Integration-of-I...ve-t107504.html Best of luck to you. I hopped on this thread because I have that laptop (it's a good one), and your issue has become my little obsession.

1) Did your 1st installation with the nLite disk contain the Intel Chipset and AHCI/SATA drivers via textmode integration? If the installation included the (same version) drivers and then you installed the full IMSM program with the same version drivers, I can see it maybe working. If your original nLite install did not contain the SATA drivers in textmode, and you installed the IMSM in bare ATA mode, that would be surprising. 2) Was this a format/fresh install? If not, I can see why you're having problems. If this was a fresh installation, I have seen folks complain about integrated WMP11 + SP3 installations. I've seen this over at the HFSLIP forum and the nLite forum. If this is a fresh installation and you don't mind doing it again, I would go conservative and at least leave out WMP11. In fact, I would also leave out IE7 - I would only slipstream SP3 and textmode add the Intel drivers. A lot of folks are having issues with integrated WMP11: http://www.msfn.org/board/Problem-with-HFS...11-t118309.html nLite may be having a rough time with SP3 + IE7 + WMP11. It looks like HFSLIP is, and I think it's more related to WMP11.

Well, I think that you are not right, because when I was installing IMSM for the first time about one year ago first I installed the drivers and then I switched AHCI mode in BIOS. And everything was warking. Since I have SP3 it doesn't work in any way. When you installed IMSM for the first time, was it just the drivers that were (TEXTMODE) included in your install disk? Or, were you in ATA, hit the executable IMSM, and it installed? If you flipped the bios to AHCI with orginal TEXTMODEd drivers present, then updated the drivers in AHCI mode, I can see how it worked. But I can't see hitting the executable in ATA mode working. But maybe... When you upgraded to SP3, were you in ATA mode? If you were in AHCI mode using the 7.8.0.1012 driver set, then that's weird. I have a 945 AHCI system at my office. I don't know when I'll get there to do it, but it was just upgraded to SP3, and I'll try to upgrade the drivers.

If you are trying to install any version of the IMSM while your BIOS is set to ATA, it will fail. I think there might be a way to get it done by messing with the registry settings by following the iaAHCI.inf, but that's going to take some effort. If you cannot get up with the BIOS set to AHCI, you may have to format and start over. If you go that route, I would use a SP3 slipstreamed disk, and install XP while the BIOS is set to AHCI mode. If you do it again in ATA mode you will probably run into the same problems. In the slipstreamed disk, I would include the following textmode/OEM drivers: 1) the Intel INF drivers and 2) the Intel SATA drivers. You may want to do it without using nLite. You can use Vitali Graf's program to OEM TEXTMODE preinstall the drivers - his program does that very well: http://www.vitaligraf.de/en/?Projects:Wind...nded_CD_Creator or http://www.vitaligraf.de/en/?Projects:Wind...reator:Download If you really want to use nLite instead, you could also go back to Fernando 1's thread in the nLite forum and follow his instructions to a "T". Just remember that if you format and do it again from scratch, you need to make sure that the BIOS is set to AHCI.

Intel just posted the latest driver set. While up in AHCI mode using version 7.8.0.1012, I updated the Intel® ICH8M-E/M SATA AHCI Controller driver from Device Manager without issue. I even ran the IMSM executable - again, no issue. There's nothing wrong with the new series as far as I can tell. But I'm having a tough time understanding how you got 7.8.0.1012 to work. Fernando 1 wrote back and said registry work would be needed, and I was hoping you could do that with an iaAHCI.inf right click install in ATA mode. His message indicated that it might not be that easy. I'm stuck. But if you can set the BIOS to AHCI and boot successfully using 7.8.0.1012 drivers and the device manager is showing Intel® ICH8M-E/M SATA AHCI Controller and the driver is iaStor.sys, then you have a weird situation going on with the latest driver set. You can also run the Intel Chipset Utility to verify that: I/O Controller: Intel® 82801HBM/HEM I/O controller hub (ICH8M) SATA Controller found in AHCI mode. If that is verified using the 7.8.0.1012 driver set, I can't tell you how to get the latest set to install beyond what I've already suggested. I think you have the latest BIOS running. You may also want to re-install the INF Update Utility. The bottom line is, though, that if you can boot in AHCI mode with the old driver set, you should be able to do it with the latest set. If you are up in AHCI mode using 7.8.0.1012 drivers, the executable should work, and/or so should a simple update driver operation in Device manager.

OK, switch your bios back to ATA. If you placed the iastor.sys file in C:\WINDOWS\system32\drivers, remove it. Then: Right click install iaahci.inf Then right click install iastor.inf If you go back to C:\WINDOWS\system32\drivers, do you see iastor.sys? If not, manually place it in the folder, and go for it again by going back into your bios, switching back to AHCI, and then boot. If this does not work, I'll ask Fernando for a little help. I did pre-load the drivers, so the switch in the bios was picked up right away. My thinking is that if XP can pick up those drivers, you should be in business. You would think that a right click install would do it, but maybe not. Another option: Have you tried to add a new device through control panel while up in ATA? I have attached the most recent Dell driver set. You may want to try them, but it should not make a difference. R154200.7z

Okay, I found it fishing around, but I'm going to wait until it's official. Yes, you have to switch AHCI on in the bios. Before you do that, while up on XP in ATA mode, try to right click install the iaahci.inf in the driver set. You might want to do the same with the iastor.inf in the driver set. You may also want to manually place IaStor.sys in C:\WINDOWS\system32\drivers if the install doesn't place it there. Re-boot, go into the bios and switch over to AHCI mode and then boot windows. Let me know how it goes.

I will try it and let you know what's up on my end. In the bios, are you in ATA mode? If so, the post installer won't work. Your bios has to be in AHCI mode. Can you post a link to the new version? I'm still seeing 7.8.0.1012 11/9/2007 - links above - for the IMSM. And the latest chipset (INF Utility) is still showing 8.3.1.1009 9/24/2007. It still show this even for the latest board/chipset, Intel® 975X Express Chipset.

That board should take the latest IMSM/SATA driver. If the older driver worked and you're having a problem with a post install of the latest IMSM, you may just want to update the driver without the installation program. That's a weird situation with the installation program...

http://www.giga-byte.com/Support/Motherboa...?ProductID=2456 You have probably already been there, but it doesn't look like the Intel Matrix Storage Manager (or the older Intel Matrix Storage Technology) AHCI driver is supported for Windows. Gigabyte has its own SATA2 RAID Driver. The driver page does not offer the Intel SATA driver, only the Intel chipset drivers. See the attached Gigabyte SATA2 RAID Driver. If your board offers an AHCI (SATA2) option in the bios, the attached should work. There is also a post install utility. I don't know if it will work on a non-R board. motherboard_driver_sata_gb_sata2raid_bootdisk_32.7z

I'm not sure if the Dell Vostro 1500 uses that board. CPU-Z doesn't give me enough info. The chipset is Intel GM965, Southbridge 82801HBM (ICH8-ME). The Intel Chipset ID Util indicates: Intel® 82801HBM/HEM I/O controller hub (ICH8M) SATA Controller found in AHCI mode I'm also not sure how old your board is. In the bios, can you choose AHCI mode? If you have a lesser chipset/board, it's possible that you cannot use AHCI, but it's interesting that you say you can in Linux because the drivers should be coming from Intel. The above zipped drivers are the latest and greatest. If your board can't use the latest, try and older Intel RAID/AHCI Software - Intel® Matrix Storage Manager. http://downloadcenter.intel.com/filter_res...mp;submit=Go%21 http://downloadcenter.intel.com/Detail_Des...al〈=eng That is version 7.0.0.1020 5/4/2007. I was hoping that michal_banszel would respond. I don't know enough about your hardware.

The above method might not work. If you don't have the drivers installed, you might not be able to boot windows. While up on XP under ATA mode, (right click) install the iaahci.inf in the driver set. You might want to do the same with the iastor.inf in the driver set. You may also want to manually place IaStor.sys in C:\WINDOWS\system32\drivers if the install doesn't place it there. Then switch your BIOS over to AHCI mode and boot. Let me know how it goes.

I'm not running across an Intel RAID/AHCI Software - Intel® Matrix Storage Manager of that edition. The latest edition I find is 7.8.0.1012 11/9/2007. http://downloadcenter.intel.com/filter_res...mp;submit=Go%21 The latest INF (Chipset) Update is 8.3.1.1009 9/24/2007. You need both, and I TEXTMODE add them before running HFSLIP. Since you are using nLite, go to this thread by Fernando 1, and you might get some relief or help. At this stage of the nLite game, you shouldn't be having any issues adding those drivers. It's been a while since I used nLite, but if you add them correctly, you shouldn't have a problem. I'm running 2K3 (x86) on the same laptop in AHCI mode. If you are in ATA mode and you try to install the IMSM, it will give you that message because the IMSM (drivers) only works with AHCI. At this point, you may want try to extract the AHCI drivers, switch back to AHCI in the BIOS, reboot, and have the OS pick up the "new device", and roll from there if you don't want to do it all over again through nLite. See the attached AHCI drivers. After the OS picks it up, you can always install the full IMSM after the fact. Good luck. Driver.7z

Hi, all. I'm on a Win Server 2K3 machine. It came with .NET 1, and has been updated - the 1.1 should be up to date. I anyone getting the following error? Microsoft .NET Framework not detected. Please install v1.1before running RAID Slipstreamer! Thanks

I always wondered about that. This is what google turned up: http://forum.notebookreview.com/showthread.php?p=2689206 or specifically, http://forum.notebookreview.com/showpost.p...p;postcount=278 If you have an Intel Mother Board (not just a chipset), this might be very applicable. If you have some other MoBo that simply uses the chipset, I would guess that the Intel VBios update is not for you. You need to check with the MB manufacturer. In conservative mode, I would simply update the MB bios, and apply the latest drivers only

Question for you guys: How does it compare to Server 2003? Since you all are the ones who just had to install it as a desktop, I'm assuming you might have done the same with 2003 (over XP). I've seen a few folks talk about the advantages over 2003 as a server, but no one has really compared the 2 as desktops. I have no reason to buy 2008. I only installed 2003 as a desktop really by chance after we ended up outsourcing our web apps. I wouldn't have coughed up the dough for 2003 as a workstation either, but boy was I impressed with 2003 as a desktop. A bit faster? Yes. Rock solid stable? Big time. 2003 just doesn't seem to labor as hard as XP. I do understand that there core differences between XP and 2003, but I also think that the Vista and 2008 core is nearly the same as 2003. With everything I've heard and seen concerning Vista, I couldn't image that 2008 could beat 2003 as a DT. I would imaging that hardware would count. Is that correct? But all things being equal, does 2008 perform better as a DT than 2003?

Let me know how it goes. I can't offer any real commentary on the sound (shouldn't be a problem), but you should not have any problems with Win2000 for the Intel chipset link above. I ran 2000 on a dell with that chipset and it ran great. Then again, with 2 Gigs of RAM, XP certainly won't be a problem. Good luck

I don't think you're going to have a problem. Relatively speaking, that's an older Intel chipset. Instead of trying to match the exact board, try the chipset: http://downloadcenter.intel.com/filter_res...mp;submit=Go%21 The latest INF seems to be available. There is an older RAID/AHCI (SATA) driver. Intel is not improving upon their SATA drivers for Win2K, but the INF drivers should get you through (before trying to hack up later SATA drivers), and for your older board, try the older SATA driver.

Tomcat76, the "Gold" source disk contains the following SVCPACK items: SVCPACK (folder) SVCPACK.DL_ SVCPACK.INF Will the test build remove all 3 items (or, if I do it manually using 1.5.0, should I remove all 3)? The removal of the SVCPACK folder is understood, and the INF calls on the KB911164.exe. I'm just not sure about removing the SVCPACK.DL_ (or how it might mess with HFSLIP or the install). Thanks

Here's 1.4.5 See the attached 1.4.2 hfslip142.zip

TC, thanks. That's what I thought - that if you included the latest cumulative IE6 update there'd be no problem. Supe, I bought it just recently on eBay. It was an open box at the right price. The seller indicated that she had recently purchased it at a local store for an app she thought she needed it for, but then realized that her old OS could handle the app. She said it was never used, much less activated. I want get it up quickly to be sure. I've never used XP as my OS before, so I have nothing to compare it to. But based on all the posts here ("b disk"), it looks like it's pretty new, and the seller's story seems to jive so far. If I was at work, I'd look at the source date stamps. Edit: Super, all files within all folders are date stamped 02/28/06.

TC, again, thanks for addressing this issue. That non-public HF (KB911164) hasn't exactly received rave reviews on the net, to the extent there is any info on it. I guess you could have guessed that I would stay in paranoid mode. If I understand what you're doing in the beta build, you are coding HFSLIP to "simply" remove the entire SVCPACK (and KB911164) from the SOURCE to produce a KB911164-less SOURCESS installation. I'm going to wait for your final build. But, could you simply remove the SVCPACK folder from the SOURCE folder prior to running HFSLIP (1.5.0 or whatever build), or would setup throw a fit (looking for SVCPACK and than stupid file)? I know MS doesn't create software with the 3rd party slipstreaming community in mind, but this one is a real "head scratcher". I'm slipstreaming the latest IE6 cumulative updates - an up-to-date, conservative, file set based on your 06/12/07 dynamic page. Thanks again. Edit: I finally bumped into this on a Russian message board. About halfway down, a poster explained on 11/22/06:

shush the paranoid... Thanks, TC. Kel., nice pickup.

Sure. This is probably overkill, but here is a WinMerge report. I can go deeper. The ASMS contains the following folders: 1, 10, 1000, 2, 5100, 52, 60, 6000, 70, and 7000 The COMPDATA folder contains mostly HTML and TXT doc. The DRW folder contains a 1033 folder and a couple files. The LANG, SVCPACK, SYSTEM32, WIN9XMIG, WIN9XUPG, and WINNTUPG folders all look like the usual stuff. I named the 7z folder the label of the disk. VX2PFPP_EN.7z