51 Reply by TigerC10

(5 replies, posted in Feedback and Support - DriverPacks Base)

The official IE7 installer doesn't integrate via standard methods properly (I think there is a lack of appropriate icons for some things).  Same with Windows Media Player 11.  However the issues with IE7 don't affect the install of the OS - but rather the actual install of the product.  The reason is that they depend on Windows Installer 3.

You need to use an IE7 Addon from the RyanVM.net forums.  I like to use the alternative pack, but that's just my personal preference.




Well, winnt.sif gets used by CD based installs, unattend.txt gets used by remote installs.  The reader for this file is very limited.  In some cases, it doesn't matter what you put in the line - as long as it's not the default it will do the other thing.  Be sure you change both winnt.sif and unattend.txt just in case (they should be identical).

Also be sure you've got the order right.  I've noticed you've got the UnattendSwitch and OemPreinstall flip flopped.  I don't think that this could cause a problem, but with such limited parsing of the file it is possible that getting them out of order could pose a problem.  See the link I posted to get the correct order of things.  I think there's a program out that will generate this file for you properly, but I can't seem to locate it.  If I find it again I'll post it for you.



However, you've got the order of the tools right.  It's just this OOBE problem.  I recommend posting at the MSDN forums, they're probably more familiar with the OOBE problem (it's very fragile - breaks easily on windows install disks).

Go to forum: Feedback and Support - DriverPacks Base

52 Reply by TigerC10

(5 replies, posted in Feedback and Support - DriverPacks Base)

You're loosing OOBE because of nLite.

Open your winnt.sif and/or your UNATTEND.TXT files inside the i386 directory on your CD.  This should be at the top:

[Data]
    AutoPartition=1
    MsDosInitiated="0"
    UnattendedInstall="Yes"

[Unattended]
    UnattendMode=ProvideDefault
    OemPreinstall=Yes
    UnattendSwitch=No
    TargetPath=\WINDOWS

[GuiUnattended]
    OemSkipWelcome=0
    OEMSkipRegional=0
    EncryptedAdminPassword=NO

The important parts here are UnattendedInstall, UnattendedMode, OemSkipWelcome, and OEMSkipRegional.

If you change the unattendmode value to something like FullUnattended then you lose OOBE.  You might also loose OOBE if you use DefaultHide and ReadOnly as well).  Likewise if you change OemSkipWelcome to 1, you will skip OOBE.  If you make OemPreinstall no, then your $OEM$ folders won't be copied.

http://www.microsoft.com/technet/prodte … 1ch01.mspx




Good luck.

Go to forum: Feedback and Support - DriverPacks Base

53 Reply by TigerC10

(43 replies, posted in Feedback and Support - DriverPacks Base)

obiwanceleri wrote:

btw in my experiment, I got an error about C:\DSPdsblr.exe not being found

That's a common problem.  I recommend using the OEMPreinstall Folder ($OEM$\$1) to get around that.  Just go into the bin and find DPsFnshr.7z - you can find all of the files you'd need to put in the preinstall folder inside this archive.  Then just run a cleanup command script at the end that deletes everything you don't want/need.

Go to forum: Feedback and Support - DriverPacks Base

54 Reply by TigerC10

(11 replies, posted in Feedback and Support - DriverPacks Base)

That's why God invented bigger hard drives! big_smile  Just copy your RIS folder to a backup location and make the alteration.  Then if it doesn't work Delete and restore! smile

All seriousness, I was just trying to let you know what I saw.  After dealing with my own issues with DriverPacks, I just wanted to give you those suggestions.  I don't know how to solve your RIS problem sad

Go to forum: Feedback and Support - DriverPacks Base

55 Reply by TigerC10

(11 replies, posted in Feedback and Support - DriverPacks Base)

I thought you were doing a NIS.  If that's the case then your SVCPACK.inf wouldn't need a new CD every time because the CD just tells the installer to look on the network for the installation stuff.  I think I read that someone was going to integrate the CPU and Chipset drivers to their boot NIS CD, and then integrate all of the other packs to the NIS Location.

Go to forum: Feedback and Support - DriverPacks Base

56 Reply by TigerC10

(11 replies, posted in Feedback and Support - DriverPacks Base)

According to your DPs_BASE.ini, you disabled QSC - Quick Stream Cache (this is something specific to DriverPacks - I wouldn't have expected google to turn anything up) AND you are installing ATI Catalyst Control Center which requires .NET to work properly.   (If you were installing the ATI Catalyst Control Panel then it wouldn't be "CCC" but rather "CCP")

EDIT:
You don't have to manually add the switchless install from RVM to the svcpack - you could just integrate it using RVM's tool or nLite.  You said it makes it easier to update by not adding it into the svcpack yourself - so you must be using one of those tools to update it.

Go to forum: Feedback and Support - DriverPacks Base

57 Reply by TigerC10

(11 replies, posted in Feedback and Support - DriverPacks Base)

I don't think this'll solve your problem, but some things you may want to consider:

1.) Enable QSC (it avoids a bug where some .CAT files are not properly copied into the svcpack directory despite having their entries added into the svcpack.inf).

2.) Make sure you've got .NET in your installation (because of the ATI thing; RVM has a nice switchless .NET 1.1 SP1 installer that can be added to your svcpack.inf)

Go to forum: Feedback and Support - DriverPacks Base

58 Reply by TigerC10

(43 replies, posted in Feedback and Support - DriverPacks Base)

You actually do, it's very frustrating in some cases.  You shouldn't need the .NET if you include a newer version since they overwrite the same calls - but the Media Center Edition stuff actually depends on files in the \WINDOWS\Microsoft.NET\Framework\v1.0.3705 directory.

Since the version of windows wasn't mentioned - I figured it was worth mentioning.  Plus, in the first post "mediactr.cab" was referenced.  Don't know if that exists for other versions or not.  It doesn't for mine because mine was an XP disk from before Media Center existed.

Go to forum: Feedback and Support - DriverPacks Base

59 Reply by TigerC10

(43 replies, posted in Feedback and Support - DriverPacks Base)

Did you attempt doing a disc install before trying NIS?  If you can't get a disc to install then there's something going wrong either before/during DriverPacks.  If you can, then there's something wrong with the way you're doing NIS.

Go to forum: Feedback and Support - DriverPacks Base

60 Reply by TigerC10

(43 replies, posted in Feedback and Support - DriverPacks Base)

That's not necessarily true, media center editions of windows XP DO need that .net stuff.

Go to forum: Feedback and Support - DriverPacks Base

61 Reply by TigerC10

(12 replies, posted in Feedback and Support - DriverPacks Base)

To quote one of the most beloved characters in all of cartoon history:
"YAY I'M DOOMED!"

Go to forum: Feedback and Support - DriverPacks Base

62 Reply by TigerC10

(12 replies, posted in Feedback and Support - DriverPacks Base)

What if I just removed the zipped packs?

Go to forum: Feedback and Support - DriverPacks Base

63 Reply by TigerC10

(12 replies, posted in Feedback and Support - DriverPacks Base)

haha, maybe.

Go to forum: Feedback and Support - DriverPacks Base

64 Reply by TigerC10

(12 replies, posted in Feedback and Support - DriverPacks Base)

Actually I did have multiple folders set up at different steps... ^_^;;

However the hard drive went out...  X.X



I don't use RVM - so it isn't easier for me to start from scratch.


I can remove some DriverPacks with the DriverPacks base - but I really want to know how to undo the whole thing.

Go to forum: Feedback and Support - DriverPacks Base

65 Reply by TigerC10

(12 replies, posted in Feedback and Support - DriverPacks Base)

Well, I could hang a DVD on the system - but I don't have any spares.

I slipstreamed all of the DriverPacks as well as the 3rd parties.  They don't fit on a CD.  I could remove the 3rd parties - how could I just take out the 3rd parties.

Go to forum: Feedback and Support - DriverPacks Base

66 Topic by TigerC10

(12 replies, posted in Feedback and Support - DriverPacks Base)

Okay, so I've been slipstreaming all of the driverpacks with success for a few months now - and it's been fantastic! big_smile

Anyway, I've just been expanding my windows install disks to DVDs because I've had the means.  Now I've got a computer with only a CD bay.  I could recreate the disk from scratch, but since I have included a bunch of windows updates and what not - I'd rather just take what I've already made and remove DriverPacks.  I did a search with little success.


So my question is this.  How does method 2 alter the installation disk?  I've already gone into WINNT.sif and removed the finisher.  I deleted the OEM folder from the disk.  Now the only thing I can think of that's left to do is remove the fake setup and restore the real one (though I'm not quite sure if that's all that's left).

Go to forum: Feedback and Support - DriverPacks Base

67 Reply by TigerC10

(43 replies, posted in Feedback and Support - DriverPacks Base)

Yeah, that's what I meant.  Sorry about the typo...

Well, instead of doing a NIS try doing a single disc installation.  If the disc installation works then it is a problem with how you're doing your NIS.  If the disc fails, then it's a problem with however you're doing things to the disc (including the possibility of DriverPacks).

Go to forum: Feedback and Support - DriverPacks Base

68 Reply by TigerC10

(43 replies, posted in Feedback and Support - DriverPacks Base)

Well I wouldn't recommend copying them to your OEM distribution folder...  That's sloppy.  I suppose that at the end of the day it all comes down to what works and what doesn't.

Try downloading the setupORG.ex_ and presetup.cmd from the site I gave in post 7.  This might confirm whether or not there's a corruption in your copy process.

Go to forum: Feedback and Support - DriverPacks Base

69 Reply by TigerC10

(43 replies, posted in Feedback and Support - DriverPacks Base)

[SourceDisksNames.x86]
1  = %cdname%,%cdtagfilei%,,\i386
2 = "%cd2name%","%cd2tagfilei%",,\cmpnents\tabletpc\i386
3 = "%cd2name%","%cd2tagfilei%",,\cmpnents\mediactr\i386
4 = "%cd2name%","%cd2tagfilei%",,\cmpnents\netfx\i386

...

mediactr.cab      = 3,,,,,,_x,,3,3
setupORG.exe= 1,,,,,,,2,0,0
presetup.cmd= 1,,,,,,,2,0,0
3ware95k.sys=1,,,,,,4_,4,1,,,1,4

filename_on_source=diskid,subdir,upgradecode,newinstallcode,spare,spare,newfilename

Do you notice that the only 2 files you have a problem with are the only two files with "2,0,0" at the end?  That's actually the default value, but since you're doing a NIS you may need to alter that...  Not sure.  I've never done NIS.



The other thing you may need to consider is a file corruption when you copy it.  It's happened to me before.

Go to forum: Feedback and Support - DriverPacks Base

70 Reply by TigerC10

(43 replies, posted in Feedback and Support - DriverPacks Base)

Bâshrat actually already addressed this on MSDN, apparently.  http://www.msfn.org/board/lofiversion/i … 57359.html

Can you post the contents of your txtsetup.sif file?

Go to forum: Feedback and Support - DriverPacks Base

71 Reply by TigerC10

(43 replies, posted in Feedback and Support - DriverPacks Base)

Wait, you're doing a NIS?  Not a disc install?

Okay, well - first thing you should know is that DriverPacks will alter your winnt.sif file - which is used for disc installations.  Since you're doing a Network Install Setup you need to add those additional/modified entries to your UNATTEND.TXT file (from what I understand, the only difference between these files should be the name).


Finally, since you said the setup.ex_ is not there anymore - just manually copy it back over.  Also copy presetup.cmd since you had problems with that one too.  If you want, try looking here:
http://unattended.msfn.org/unattended.xp/view/web/35/

They have the files available for download if you don't want to re-copy them from the disc.

Go to forum: Feedback and Support - DriverPacks Base

72 Reply by TigerC10

(43 replies, posted in Feedback and Support - DriverPacks Base)

Don't just copy the I386 folder off of the windows disk.  Copy the entire disk.  The cmpnents folder has some .NET stuff integrated to the installer, and if you have a tabletPC or media center option the compnents folder contains that data too.


Also check your I386 folder for "SETUP.EX_".  It is supposed to be expanded to "SETUPORG.EXE".

Go to forum: Feedback and Support - DriverPacks Base

73 Reply by TigerC10

(12 replies, posted in Feedback and Support - DriverPacks Base)

Helmi wrote:
JeremyNNT wrote:

[...] and using the QSC because even though DPBase says not to use it for method two, the tutorial says to use it for all new versions.

BASE is actually saying that?

Are you using the English version or one of the translations?
I don't remember it saying that, but then again I have only been using the (created by me) German translation so I can't really remember...

Yeah.  The base says that.  When I had my problem a few months ago I found that because I wasn't enabling the QSC it wasn't adding the .CAT files to the svcpack - but it did alter the svcpack inf to include the lines for the corresponding updates.  When I tried to use the bug tracker to report the issue my account never would activate...  Never could log in. lol Anyway I was afraid to enable QSC because the base said it was recommended not to.  It's not a big deal though.



Anyway, despite being told to use QSC for method one, you should enable for method 2 anyway so that you don't have that issue.

Go to forum: Feedback and Support - DriverPacks Base

74 Reply by TigerC10

(12 replies, posted in Feedback and Support - DriverPacks Base)

Woah, yeah... the screen resolution is kinda high...  Try 1600x1200 if you know your monitor/video card can handle it.  1024x768 should be ample until you actually get into the system...  Worst case senario use 800x600 and you know it'll work.

Go to forum: Feedback and Support - DriverPacks Base

75 Reply by TigerC10

(12 replies, posted in Feedback and Support - DriverPacks Base)

You're all over the place with your tools...

You shouldn't need to use nLite to rip the source disk.  Just copy all of the files from the CD to a place on your hard drive.  It's easier that way.

Then you should create your winnt.sif file (just in case RVM uses it, but it probably doesn't).

Then you can use RVM to update everything.

Then you should integrate the DriverPacks (driverpacks does alter your winnt.sif file, so creating it after the DriverPacks integration will get rid of the alterations needed).

Finally you should create a bootable data disk ISO with Nero, instead of using RVM or nLite (they can mess stuff up).  CDGUI is good too.  After that burning it shouldn't be a problem.

EDIT:
Your winnt.sif file seems to still have the data altered by DriverPacks, so I think that it's just that you're using a different tool for making your iso.

Go to forum: Feedback and Support - DriverPacks Base