g-force

Man, you`re kidding, aren`t you? Did you ever tried to install without that crap of drivers? I`ve never seen XP needed integrated driver for installing in a VM.

This is a little SFX, that adds "makecab" and "expand" to your contextmenu: http://www.file-upload.net/download-156488...Expand.exe.html

Hi & Welcome Mapster! Is "Norwegian XP" fully localized or is it English with MUI ?

The word you both are looking for is "winntbbu.dll", which modifies the Setupscreen. A User "Bussibear" @ German-WinLite has made a couple of those Setupscreen - take a look: http://www.german-winlite.de/wbb/index.php...amp;postID=1561

@specter: Bye bye @admin & mod: this is WAREZ!

It`s explained in nLite itself that removing of Outlook Express causes problems with Outlook. So you`ve found the solution yourself and made a new nLite-XPCD - so why to reinstall OE? It`s not possible anyway.

THX 4 Update - works like a charm on german MSN!

Start your check-out here: http://forum.driverpacks.net/viewforum.php?id=23

Please attach (not paste) your "Last Session.ini" to let us know what you removed.

You should turn on the lights by yourself by giving us more informations. What hardware is used, you`re talking about "Touchscreen". Which files have been integrated, and how were they integrated? About Intel-Textmode: http://www.msfn.org/board/index.php?showtopic=107504

I don`t know where these files come from or what they are good for - but there`s no "example.inf" and "example.sys". INF and SYS are needed in every driver I know and integrate. Try DriverGrabber or DoubleDriver on a system where this hardware is pretty installed to save the driver-files.

Like "mooms" said, the "DriverBase" is the solution. Integrate all unpacked DriverPacks is "too much" for nLite, it´s too big. And of course, the ChipsetPack doesn`t contain any "txtsetup.oem", which is absolutly needed for this way of integration - so this way is useless.

Maybe you create a "winnt.sif" with an eye, that takes a look at the sticker on the computer... Sorry for sarcasmn, but I´m wondering you`d like to setup 100 DELL-PCs and don`t know how. Are you new to business? nLite can`t be the answer due to it`s licence - no commercial use. In Domains at 100 PCs normally a Volume-Licence by MS takes place. You want to use 100 different keys? I`m still wondering...

No, you got to build an addon first. Search the forum for addon, addon-maker, createur

To put a Hotfix in "svcpack" and add manually a line in "svcpack.inf" is the "classic method" of Hotfix-Integration. It`s not what we call "Slipstream", because the Hotfixes are installed while XP-Setup. Some Hofixes cannot be slipstreamed directly with nLite, so nLite falls back to this "classic method".

If you run "setup.exe /admin" you create an Admin-Install of Office 2007. You generate an "mysetup.msp" which is copied to folder "Updates". Office-Setup will read this file and execute the Setup like you wanted. If there`s a last windows that don`t closes, you missed a setting. I only got a german Office-Setup, but please run "setup.exe /admin" again, load your pre-created .msp and check the settings:

If you want to create RAID-5 you will have to use all of your 3 HDDs. If you have created a RAID with 2 HDDs (and left 1 HDD) it will be RAID-0 or RAID-1. That`s not what you wanted - but you did it... There is no way to change your 2-HDD-RAID to RAID-5 (with 3 HDDs). It`s still unclear how you create your RAID. I´m used to create my RAID in the BIOS - no drivers or OS is needed.

After reading this article you will know that this KB ist only important when the ISO is created on an Intel-Machine and then installed on an AMD-Machine. Link: http://support.microsoft.com/kb/953356/en-us Try to create a XPCD with slipstreamed SP3 on the AMD-Machine and then install it on that PC - it should work without problems.

Please read this topic: http://www.msfn.org/board/index.php?showtopic=131668

Your question about the drivers: I downloaded R111550.exe from HERE as an example. I unpacked the EXE with WinRar to get these folders: "R111550\Windows\tiinst1" The last folder "tiinst1" contains the drivers, everything else is probably unneeded. Copy all your Rxxxxxx.exe to a folder "DELL", extract them with WinRar, and point nLite to "DELL" by using "Insert > Multiple Driver Folder". nLite will only integrate folders containing an ".inf" - don`t care about the unneeded files. Enjoy.

John is wrong, GrofLuigi is right. DOTNETFX and VALUEADD are on all genuine XPCDs. Here`s a directory list of XP SP3 (german): cmpnents DOCS I386 SUPPORT VALUEADD cmpnents\netfx cmpnents\TABLETPC cmpnents\netfx\i386 cmpnents\TABLETPC\i386 I386\ASMS I386\COMPDATA I386\DRW I386\LANG I386\SYSTEM32 I386\WIN9XMIG I386\WIN9XUPG I386\WINNTUPG I386\ASMS\1 I386\ASMS\10 I386\ASMS\1000 I386\ASMS\2 I386\ASMS\5100 I386\ASMS\52 I386\ASMS\60 I386\ASMS\6000 I386\ASMS\70 I386\ASMS\7000 I386\ASMS\1\default I386\ASMS\10\msft I386\ASMS\10\policy I386\ASMS\10\msft\windows I386\ASMS\10\msft\windows\gdiplus I386\ASMS\10\policy\msft I386\ASMS\10\policy\msft\windows I386\ASMS\10\policy\msft\windows\gdiplus I386\ASMS\1000\MSFT I386\ASMS\1000\MSFT\WINDOWS I386\ASMS\1000\MSFT\WINDOWS\GDIPLUS I386\ASMS\2\default I386\ASMS\5100\MSFT I386\ASMS\5100\MSFT\WINDOWS I386\ASMS\5100\MSFT\WINDOWS\SYSTEM I386\ASMS\5100\MSFT\WINDOWS\SYSTEM\DEFAULT I386\ASMS\52\msft I386\ASMS\52\policy I386\ASMS\52\msft\windows I386\ASMS\52\msft\windows\net I386\ASMS\52\msft\windows\net\dxmrtp I386\ASMS\52\msft\windows\net\rtcdll I386\ASMS\52\msft\windows\net\rtcres I386\ASMS\52\policy\msft I386\ASMS\52\policy\msft\windows I386\ASMS\52\policy\msft\windows\networking I386\ASMS\52\policy\msft\windows\networking\dxmrtp I386\ASMS\52\policy\msft\windows\networking\rtcdll I386\ASMS\60\msft I386\ASMS\60\policy I386\ASMS\60\msft\windows I386\ASMS\60\msft\windows\common I386\ASMS\60\msft\windows\common\controls I386\ASMS\60\policy\60 I386\ASMS\60\policy\60\comctl I386\ASMS\6000\MSFT I386\ASMS\6000\MSFT\VCRTL I386\ASMS\6000\MSFT\VCRTLINT I386\ASMS\6000\MSFT\WINDOWS I386\ASMS\6000\MSFT\WINDOWS\COMMON I386\ASMS\6000\MSFT\WINDOWS\COMMON\CONTROLS I386\ASMS\70\msft I386\ASMS\70\policy I386\ASMS\70\msft\windows I386\ASMS\70\msft\windows\mswincrt I386\ASMS\70\policy\msft I386\ASMS\70\policy\msft\mswincrt I386\ASMS\7000\MSFT I386\ASMS\7000\MSFT\WINDOWS I386\ASMS\7000\MSFT\WINDOWS\MSWINCRT I386\DRW\1031 I386\DRW\1033 I386\WIN9XMIG\ACROBAT I386\WIN9XMIG\CMMGR I386\WIN9XMIG\DEVUPGRD I386\WIN9XMIG\DMICALL I386\WIN9XMIG\DVD I386\WIN9XMIG\EASTMAN I386\WIN9XMIG\FAX I386\WIN9XMIG\HPTOOLS I386\WIN9XMIG\IBMAV I386\WIN9XMIG\ICM I386\WIN9XMIG\IEMIG I386\WIN9XMIG\MAPI I386\WIN9XMIG\MODEMS I386\WIN9XMIG\MSGQUEUE I386\WIN9XMIG\MSI I386\WIN9XMIG\MSNEXPLR I386\WIN9XMIG\MSP I386\WIN9XMIG\NECKBD I386\WIN9XMIG\NECPA I386\WIN9XMIG\NECWPS I386\WIN9XMIG\OCTOPUS I386\WIN9XMIG\OEWAB I386\WIN9XMIG\PRINT I386\WIN9XMIG\PWS I386\WIN9XMIG\RUMBA I386\WIN9XMIG\SETUP I386\WIN9XMIG\TRANSACT I386\WIN9XMIG\WIA I386\WIN9XMIG\WMP I386\WIN9XMIG\ACROBAT\FILES I386\WIN9XMIG\MAPI\80 I386\WIN9XMIG\MAPI\801 I386\WIN9XMIG\MAPI\802 I386\WIN9XMIG\MAPI\803 I386\WIN9XMIG\MAPI\98MAPI I386\WIN9XMIG\MAPI\98OMI I386\WIN9XMIG\MAPI\DLL I386\WIN9XMIG\MAPI\EX40 I386\WIN9XMIG\MAPI\EX40A I386\WIN9XMIG\MAPI\EX40SP3 I386\WIN9XMIG\MAPI\EX40SP4 I386\WIN9XMIG\MAPI\EX50SP1 I386\WIN9XMIG\MAPI\EX50SP2 I386\WIN9XMIG\PRINT\BLAINF I386\WIN9XMIG\PRINT\DTCINF I386\WIN9XMIG\PRINT\ENTINF I386\WIN9XMIG\PRINT\PERINF I386\WIN9XMIG\PRINT\SBSINF I386\WIN9XMIG\PRINT\SRVINF I386\WINNTUPG\ENTINF I386\WINNTUPG\MS I386\WINNTUPG\OEM I386\WINNTUPG\PERINF I386\WINNTUPG\SRVINF I386\WINNTUPG\MS\MODEMSHR I386\WINNTUPG\MS\SNA I386\WINNTUPG\OEM\DIGI I386\WINNTUPG\OEM\EICON I386\WINNTUPG\OEM\EQN I386\WINNTUPG\OEM\SPX I386\WINNTUPG\OEM\TIGERJET I386\WINNTUPG\OEM\DIGI\ASYNC I386\WINNTUPG\OEM\DIGI\ISDN I386\WINNTUPG\OEM\DIGI\REALPORT I386\WINNTUPG\OEM\DIGI\ISDN\BRI I386\WINNTUPG\OEM\DIGI\ISDN\PRI I386\WINNTUPG\OEM\SPX\MPS SUPPORT\TOOLS VALUEADD\3RDPARTY VALUEADD\MSFT VALUEADD\3RDPARTY\MGMT VALUEADD\3RDPARTY\MGMT\CITRIX VALUEADD\MSFT\FONTS VALUEADD\MSFT\MGMT VALUEADD\MSFT\NET VALUEADD\MSFT\USMT VALUEADD\MSFT\MGMT\CIMV2R5 VALUEADD\MSFT\MGMT\IAS VALUEADD\MSFT\MGMT\MSTSC_HPC VALUEADD\MSFT\MGMT\PBA VALUEADD\MSFT\MGMT\WBEMODBC VALUEADD\MSFT\NET\NETBEUI VALUEADD\MSFT\NET\TOOLS VALUEADD\MSFT\USMT\ANSI

This is a known issue - wondering nobody here told you? Reason isn`t clear yet, but it happens even with nLite and classic integration of SP3 with Vista as Host-OS. You found the solution by yourself - use XP as host.

Take a look at this: http://downloadcenter.intel.com/Detail_Des...13〈=eng

It`s "KB955839" that causes the problem - don`t integrate it.

I´m interested - but it`s russian. I can`t understand it - maybe a translation would help. Could you do that for us?