[johnhc]

TranceEnergy,
I agree with you about CFP. People have been asking for switches for some time now (years). I am surprised nothing has happened. I did place a request in the Wish-List topic to see if we can get some action on the next release or so.

I have an AMD FX-57, fairly fast but single core. I am doing the nLite and VMware Server work to get ready for an upgrade to a quad core Phenom if AMD will just get busy. I will keep Orthos in mind - thanks.

Sorry, I can't answer your DirectX question - hopefully Kurt can help.

Enjoy, John.

[Kurt_Aust]

JohnHC:
If you think it's causing you problems, you can drop the ShutDown command, you'll just have to reboot manually. It's really just the equivalent of choosing Restart from the start menu without closing all your applications first. Properly written applications should have no problem with it.

I took a look at that post on the Comodo forums, it looks like a similar method to that used on v2.4. However, I have no intention of getting into repackaging switchless installers for this guide, partly because I don't want to have to say "Trust me".


TranceEnergy:
As I understand it you don't need the x86 aspects of DirectX on Win XP x64. DirectX is an API that interfaces to the x64 graphics & sound drivers, so as x64 systems don't have (and cannot use) x86 drivers, nuff said.

[TranceEnergy]

Kurt:

As you say Win XP X64 doesnt need the x86 side of directx, yet it is shipped with it is it not?
But that x64 cant use x86 drivers i know of course. I am just merely curious at this. I am sure that the people releasing these packs know what they are doing, but i would just like to see it confirmed somehow that it is indeed correct.

[johnhc]

Kurt,
It was not my intention to suggest you or anyone use the process Buhric identified to create a CFP installer. I was hoping to hear back about the 'plenty' of switches he said were in CFPCONFG.EXE. I ran the switch finder against it and it found no switches. I guess I was also hoping that you had methods to extract switches when you knew the correct module.
Enjoy, John.

[Kurt_Aust]

TranceEnergy:
DirectX update will install the x86 SDKs on XP x64, but of course only developers would ever use them. Similarly it installs the DirectX 10 SDKs (does the same on Windows 2000), you don't need them, but they do no harm either.

JohnHC:
Sorry to shatter your illusions, but I have no such tricks up my selves. If it's not documented, then all I can do is use trial & error with common switches.

[johnhc]

Kurt,
Should the DirectX_9c entry still have EXTRACT on it?
Enjoy, John.

[Kurt_Aust]

JohnHC:
Yes, as the main post has not been changed as yet. The alteration will occur with next month's updates.

[ricktendo64]

FYI over @ RyanVM there is a updatepack for XP x64 http://www.ryanvm.ne...opic.php?t=6400

[TranceEnergy]

ricktendo64, on Jun 20 2008, 12:02 AM, said:

FYI over @ RyanVM there is a updatepack for XP x64 http://www.ryanvm.ne...opic.php?t=6400

I think we know about it.
Slight problems with it tho, it approaches updating only updates, not also IE to 7 (or newest). Whether we like it or not, IE is integral part of windows.
Currently Nlite does a kick a** job of integrating updates individually, so it's more suited to one's system.

If the maker of the update pack would either delete IE6 updates, or start using IE7 updates, it might be the better alternative. As it is now, it aint, imho.

[johnhc]

I sent a PM to Buhric on the Comodo forum asking about the 'Plenty more switches' and he responded:

Quote

Here's the switches i was able to find out:
-a --> performs a scan
-c --> not sure exactly what it does see -x
-d --> performs an installationg diagnostic
-i --> installs the software
-k --> starts the config wizard
-m --> see -x (I think its to import your settings from a file)
-o --> Show the "Offer" page
-r --> Reboots your pc
-s --> silent switch, when used with -i performs a silent install
-u --> uninstall comodo
-x --> when used without any argument gives out the following error
"Invalid Argument" Please use -c switch to specify valid filename

My guess is that -x is used to export the firewall setting to a file specified by -c, and -m is to import a file specified by -c

Unfortunately, still not very useful. We can only hope the CFP development team will do something.
Enjoy, John.

[Kurt_Aust]

I've just done a quick test with the switches supplied, the -c, -m & -x switches seem to work as suggested, so you'd be looking at a section like this:

rem firewall
"%ProgramFiles%\7-Zip\7z" X %Source%AddOns\CFP_Setup_3.0.25.378_XP_Vista_x64.exe -O%Temp%
%Temp%\CFP_Setup_3.0.25.378_XP_Vista_x64.exe -s
Del %Temp%\CFP_Setup_3.0.25.378_XP_Vista_x64.exe
"%ProgramFiles%\Comodo\Firewall\cfpconfg" -m -c%Source%AddOns\CFPsettings.cfg

Mind you, I'd exercise extreme caution with this.

[johnhc]

I had decided to try to let WPI do the reboot after Kurt_Aust's install procedure completes. I discovered that any of three reboot options I tried did not work. This turned out to be a 64 bit problem. WPI guru, mritter, has been working on making WPI 64 bit compatible the last few days and has sent me a Beta that seems to solve the problems. I was using WPI to do some installs for me and when I added a reboot, it seems to be OK. I have more testing and have never tried a full install. The Windows Personalizations run to completion before WPI starts. Since I started this testing, I removed the shutdowm from Kurt's procedure and have seen no more of the missing Quick Launch folder problem I saw before. I think this is useful because it removes the need to guess at a shutdown delay, or specify a huge delay to avoid problems.

Any comments are more than welcomed.

Enjoy, John.

[5eraph]

TranceEnergy, on Jun 20 2008, 10:51 AM, said:

ricktendo64, on Jun 20 2008, 12:02 AM, said:

FYI over @ RyanVM there is a updatepack for XP x64 http://www.ryanvm.ne...opic.php?t=6400

I think we know about it.
Slight problems with it tho, it approaches updating only updates, not also IE to 7 (or newest). Whether we like it or not, IE is integral part of windows.
Currently Nlite does a kick a** job of integrating updates individually, so it's more suited to one's system.

If the maker of the update pack would either delete IE6 updates, or start using IE7 updates, it might be the better alternative. As it is now, it aint, imho.

I don't include IE7 because not everybody wants it. nLite still does a kickass job of integrating it on top of my pack though, even with the two IE6 updates that I include.

I don't mean to steal Kurt's thunder, but my pack was brought up...

You have some great stuff here, Kurt.

This post has been edited by 5eraph: 29 June 2008 - 05:29 PM

[Kurt_Aust]

JohnHC:
If you're running WPI, that will definitely cause a conflict with the shutdown command at the end of Run1_XP-64.bat. I'm going to assume that WPI is kicked off by GUI RunOnce, which is executed after the shutdown command is issued.

One thing you could try is renaming WPI.hta to R2WPI.hta and add this to line to Run2_XP-64.bat [WPI\R2WPI.hta]. Obviously you'll have to activate the SchTasks line as indicated, be sure to move all security software (esp Comodo) installs after WPI.


5eraph:
No offense taken, if your pack had existed before I wrote this guide, I probably wouldn't have bothered. Similarly when I wrote my guide for W2K, OnePiece's pack didn't exist either. At the time there was no real alternative option.

[johnhc]

Kurt,
I've never had any conflict with your procedure and WPI. Before I removed the shutdown in your process, WPI always ran after your reboot and worked fine. Since I removed your reboot, after your process finishes, the 'Personalizations..' run, then WPI comes up and runs fine. The reboot I have at the end of my WPI installs waits for the last one to finish, then starts the reboot. There are no terminated processes and I have not seen the missing Quick Launch folder.
If I haven't mentioned before, I am creating a user account (with Administrator privileges) with nLite and that account is what is running for your process and WPI.

BTW, I am glad you did create this procedure. I especially like that I can install VMware Tools early but also like the flexibility that comes with your hotfix procedure. I really am not too crazy about turning this over to someone else to make the decisions. Thanks again for creating it and your continued support.

Enjoy, John.

[TranceEnergy]

I would just like to add that i like this approach Kurt has, and as i always used anyway before i came across it , the single hotfixes integration i mean instead of packs.

The pack is nice tho, but sometimes i am doing installs without IE at all, then it becomes excessive baggage, as i have my presets and similar, that keeps the install IE free, as close as anyway.

Imho the pack would be better off, if IE and outlook f.ex updates were in a separate pack/s.

[TranceEnergy]

I just got word from developers of punkbuster that future version of punkbuster installer will not show error messages is previouvly here mentioned was shown if windows firewall was removed, even if installer is launched with no prompts/no display command lines. Basically this just made my day. Hopefully new version will be released soon.

This just goes to show that telling people what doesnt work/or dislike etc, can sometimes actually be done something about.
Total silent windows install with everything ready on first login? Yes thank you very much.

[johnhc]

Kurt,
You may know about this, but I have found an audio driver that is suppose to work for 64 bit Guests. I attach one I found on the VMware web site and a signed one I found via Google. I have been trying to run VMware Server 2.0RC1. It should have an audio(VMaudio) driver as part of VMware Tools64, but the audio fails to install when the tools install. I tried these drivers on my VM and have no luck so far - still 'no audio device'. I have an open thread on the VMware forum and if I don't learn something soon, I will try integrating the signed VMaudio driver and see if that works.

This driver is listed to work on versions 1.0.4, 1.0.5 and 1.0.6. If you give it a try and are able to get audio to work, please let me know how you do it.

Enjoy, John

[Kurt_Aust]

July updates

Deletions:
Hotfix\290-WindowsServer2003.WindowsXP-KB941644-x64-ENU.exe
Hotfix\350-Windows-en-US-KB943729-x64_b9de932f286c62685fed238462a38d734b36ff18.exe

Modifications:
Move (& rename) RunOnce\WindowsServer2003.WindowsXP-KB951376-x64-ENU.exe to Hotfix\415-WindowsServer2003.WindowsXP-KB951376-x64-ENU.exe

Delete the \DirectX_9c folder, instead place the unextracted redistributable at \RunOnce
Moved Windows Defender to \AddOns (not in the same class as .Net et al)

Additions (at \Hotfix):
@ 430-Windows-en-US-KB943729.exe [890,936] Optional, Group Policy Preference Client Side Extensions, updated version
@ 440-WindowsServer2003.WindowsXP-KB951748-x64-ENU.exe [5,106,736]

Important change at step 7 of the process, the RunOnce file should now be (no more "pause"):

TimeOut /T 40
CMD /R %Source%Run1_XP-64.bat

Application support (\AddOns):
Added
Opera
Orbit Downloader
Tweak UI x64 extracted (installed) if 7-zip present

Modified
Rewrote ChOwn*.bat files & created links for easier usage
Do NOT extract VMware tools, just copy windows.iso to \AddOns (again needing 7-zip)

Removed Azureus (they've blocked the silent install switch in the latest version)


JohnHC:
As I understand it VMware server does not emulate audio hardware, so I don't think any driver will help.

[johnhc]

Kurt,
I am now listening to Internet radio on my 64 bit guest and I think you can also! Look in your .vmx file (VM not running) and change your virtual device as follows:

sound.virtualDev = "es1371"

Mine originally said sb16 instead of es1371. That should cause you to show a sound adapter (enable it in guest configuration) in Device Manager. Install one of the drivers I posted and see what happens - good luck! I am running 2.0.0RC1 and VMware Tools contain the driver for me.

Thanks for the July update. I guess you know nuhi fixed the KB951376 integration problem in nLite 1.4.7. I tried it last week and it seems to work fine.

I have not looked through all you updates and will soon. Good idea on the VMware Tools not needing extracting. I noticed for RC1, they have separated 32 and 64 bit items (e.g. VMware Tools64.msi) in the .iso. I extracted it and deleted all that I could identify that I thought I did not need, then 7-ZIPped it to about 16 MB. The ADDLOCAL=ALL switch causes a problem (failure to register DLL) so I use only '/i <file name> /qn /norestart' which seems to work fine.

Have fun with your sound, but please let me know if it doesn't work.

John