big poppa pump

Actually simply calling msiexec does work. This is what I have in my svcpack.inf and it works perfectly: msiexec /I Microsoft Windows Journal Viewer.msi /qn

I am not sure if I understood your question. Are you asking if the si3112r controller will support single drives on each channel seperately rather than raiding them together? If thats the case then the answer is Yes!

First of all do you know what raid controller your motherboard uses???

asus a7n8x-e Deluxe yep Really need to add the driver to it since in vmware it doesn't seem to detect my A: There are several topics for adding raid drivers to your cd in this forum. Use the search function to get your answer.

Have you tried using a different name for the computer??

Then read all the topics related to SI3112r in this part of the forum. And why the heck are you posting the same thing in two diferrent forums???? edit........SI3112r

Yes I agree with you. This program installs 2 services that require systemrestore to be enabled and you are always going to get that nag if systemrestore is disabled. The only option is to use a batch file to enable systemrestore temporarily, then install the program and then disable systemrestore again.

What cluster size did you use on your Raid partition???? The default 4k partition or did you use a higher cluster size???

Stop being lazy and do a search in google for the program. @Maverick - I also use metapad instead of notepad and I found it much easier to replace metapad during installation itself rather than do all the crap by replacing it all over the place. Rename metapad.exe to notepad.exe, then do a makecab notepad.exe, then use modifype on notepad.exe and finally replace the original notepad.ex_ with the modified metapad/notepad in the I386 folder.

One word that will describe the whole problem. ECS

This is old news. Most of the people know to stay away from the Nvidia IDE drivers.

Why are you posting this all over the forums? You posted a similar topic in the unattended windows section.

Use winrar to extract all the files from port95nt.exe. Once extracted you will see that it uses an installshield installer. Use the standard installshield swtiches to install the program.

NVM! Please close this topic!

Quick question! If I add/delete files from Driver.cab and SP2.cab, do I need to make any edits/changes other than dosnet.inf and txtsetup.sif???

None.

Make sure that you are specifying the right path in winnt.sif!

You would have got a faster reply had you posted in the right forum.

Yes! The CC can be installed using the following switch: xxxxxxxxx.msi /QR REB0OT=REALLYSUPPRESS The CC has some additional options, but IMHO the CP is much better and not as bloated and resource hogger as the CC. Stick with the CP!!!

I think you are confusing yourself between the CC (Control center) and the CP. The CP can be easily installed using the normal .iss method. The CC can be installed using the msi file in the CC folder.

Thats because the main installer for 4.9 has changed. You need to install each individual component - driver, CP, WDM and record the .iss files each one of them.

I think you may have to change all these: i386\ntoskrnl.ex_ i386\ntkrnlmp.ex_ inside driver.cab, sp1.cab and/or sp2.cab. ntoskrnl.exe ntkrnlmp.exe ntkrnlpa.exe ntkrpamp.exe

Use something like Metapad (search in google) instead of notepad and open up txtsetup.sif using Metapad. The line numbers are displayed in the status bar in Metapad.

Thats because the file is bieng replaced by windows from SP2.cab and/or Drivers.cab. To be on the safe side I edited the files in all 3 instances - i386, SP2.cab, Drivers.cab and I have absolutely no problems at all with my custom bootscreen.

One word - SEARCH!!!!