evilvoice

deleted

http://www.msfn.org/board/index.php?showto...899&hl=wisptis# but, in executing this reg fix, it will break journal viewer...so what im thinking is maybe you can look at what reg settings the msi imports on install, and compare to the list in the wisptis fix, and if you see corresponding keys, delete them...

well, i know a lot of people posted a fix, and it does deal with registry keys...maybe looking through the msi at the reg keys and comparing to whats removed so adobe doesnt open wisptis will alleviate you having to install journal.

did you get wisptis removed?

deleted

deleted

uhm, does this version still have the wisptis problem, where wisptis gets loaded everytime you start reader, but once you close reader, wisptis is still running?

deleted

ok, time to rebuild netfxsp1...LOL.

and this works with msiexec not being in the exe?

well, then, I dont mean to diss on serialzs, but I have no idea why this thread is a sticky...if yours does the exact same thing that this one will do in the end, and yours works currently...i personally think this thread should be unstickied...sorry serialzs, but I just dont get the differences between the 2, if there are any.

well, thank you...I only really read the first post...but isnt your method the exact same thing being tried here? I mean, what is the difference between the 2...why is one method better than the other (other than the problems this one had...if this method worked, what are the benefits of this method?)

ie6 and msoe add to runonceex...

why couldnt we combine the methods of pyrons "drivers from cd" and this thread and figure out some method to fix this...using pyrons setup.exe, it loads presetup.cmd, which we can run drvz.exe form this (start /wait command prolly needed), and then use the rest of serialzs method...like having devicepath.exe instead of setdevicepath.exe from pyron...7za.exe...seriously, I think if someone wanted to, they could combine the 2 methods and get the "guide for compressed drivers" working...

I notice you have one big one...is this all the other reg files combined into one...if so I could fix that one up and send that one to you...but if the others contain stuff not in the big reg file, I could fix all of them up and send you those. Shouldnt take me long as most of the settings I have, so I know what they are supposed to be...yea, some of the ones posted here are wrong...and I could tell, the ones that I know are wrong are from this thread...I just havent gotten around to making a post here as to which ones are wrong.

deleted

deleted

deleted

deleted

deleted

deleted

i can send sp1's msiexec.exe, but dont have sp2 on my pc yet...actually, to get the error, all you have to do is extract msiexec.ex_ from sp1 and run it on a sp2 machine (if it errors) this is how I got the sp2 error...and before anyone replies saying that is normal...I got the same error when having it inside the .netsp1 pack, so dont think its only because im running it without a command.

JohnnyDo, as I was going through your reg tweaks, I found some errors...not a lot, but some...if I get time, Ill go through and fix them and send them back to you...also, for tcpip parameters, you use dword values...is this correct, or should they be strings? stuff like "DefaultTTL" And also, I would like to add that first I run HKCU at cmdlines.txt, then I run both HKCU and registry .reg during runonceex (I rerun HKCU just to make sure settings are applied), but I decided to make a inno setup installer for the reg tweaks...has anyone else thought of doing this, or done it? Ive completed it, just havent applied it...my reason for doing this is for some reason, some tweaks never get put in...im thinking its because of some of my heading might be interfering with the install...so I changed to inno setup and will test how it goes...but I was able to remove some errors I found...so worse comes to worse, if some of your settings arent applying, get ISTOOL 4 and dump your reg settings inside, then look through each item and see if it looks right...reg_expand_sz does not import correctly, so thatll look weird...basically if you see any value with hex(2) in it, change the key from strings to expandsz, and type in the word, not the numbers (hex(2) comes like 25,00,50,00 and in inno setup, it needs to read %systemdrive% thats what I mean)

do you have OemPreinstall = "Yes" in your winnt.sif?

uhm...these both have been posted in the really long registry tweaks thread...do a search for sound, since the beginning...and it should return with a registry tweaks thread..power configuration is in that thread also.