RyanVM

Heh, my SFX install (7zip based) is 11.7MB B) Still no luck on the LiveUpdate settings, though

I've never used the system root varable, I always use the "systemdrive% variable myself.I love these forums... Paul %systemroot% just points to the windows directory

THANKS! If you're talking about removing Microsoft's VM, they released a tool to do it for you. Just search for unmsjvm.exe

Does anybody know of a registry tweak which will accomplish this task?

No, but that's good to know. Thanks

Does anybody know how to change LiveUpdate settings so it's installed with them in place? I pulled Settings.Default.LiveUpdate from the SFX archive and found the relevant keys (PREFERENCES\EXPRESS_MODE\ENABLED=YES and such), but after modifying the keys and repacking the file into the archive, it seems to completely ignore those settings once LiveUpdate is actually installed. Anybody have a clue how to make the settings stick?

OK, I tried searching for the answer, but IBB is pretty much useless in its search functionality. What are the settings used for makecab when recompressing driver.cab (after combining it with the other driver cabs) that allows for faster decompression? Is it just lowering CompressionMemory?

I use Orca for changing file version/size info. Also, I use it for changing the product name (like Acrobat Reader 6.0.2). And I've on occasion used it for removing file references.

Ah, I thought you were replying to mazin saying that 2.5.56 was out.

2.0.3790 is what I've got. It's the XP SP2 build.

Just so you guys know, if you're willing to do some MSI hacking, you can actually remove all of the other files in the LuMMInst directory. Just make a note of the file names so you can remove their references using Orca or WinINSTALL LE. I've also been able to repack lsetup.exe to extract silently, as it's nothing but a WinRAR SFX archive. Unfortunately, I've also tried editing Settings.Default.LiveUpdate to have Express mode enabled by default, but that setting for some reason didn't appear to stick. I've tested all of this out and it works beautifully. With the 9/11/04 virus defs, my whole SAV install package is 11.7MB 7-zip compressed.

If you're booting from the CD, you need to edit txtsetup.sif, not dosnet.inf

If it uses a registry entry, you could actually edit the MSI file to have it right the registry entry with your serial number already in it.

Check your System control panel. Also, a quick check to see if it's integrated is to see if you have the file Win51.sp2 on the root of your CD.

Well, I have a newer build of Orca, but I doubt it'll really matter.

The one thing about that guide is that it appears at least to me that PrintMe's only being removed via registry entries, where I actually remove the files and any references to them in the MSI. Other than that, that guide is wonderful

Search for gosh's post on editing syssetup.dll

That makes sense (regarding creating the AIP on a system without SAV installed). I think the newer scan engine comes with the 9.0.0.1400 patch, as the one computer I've got SAV9 installed on is also using 1.2.0.13.

If you ran LiveUpdate with 2.0, it would say it's up to date. Heck, when 2.0 was the current version, I had to manually update all my PCs from 1.8 because it said they were up to date.

wow, I'm glad to see you guys figured out the Si3112 problems. Nice work B). Now for that pesky NVRAID stuff

The problem you're experiencing is normal for an unattended install. The reason copying from the floppy is failing is because you have OEMPreinstall=Yes in your winnt.sif file. However, that's a required key for some other parts of the unattended install . The solution for that is to integrate your SATA drivers into the unattended CD, by using either Bashrat's MassStorage driver pack (sticky at the top of the page) or by following the instructions found on GreenMachine's Page. If you choose to go the second route, be sure to read the notes at the bottom of the page.

I use both to do different tasks. I'm about to take off for the evening, but I'll get back to you some time about it.

You can edit syssetup.dll to rename it.

It installs MSXML 4.0 SP2, so I guess I don't understand the question.

Have you ever used WinINSTALL LE or Orca, trekker?