mythosaz

I hate to just throw in "Me Too!" posts, but I see this on my Dell D410 laptops.

The cab being loaded or not depends on the KEY used.

The following is the [WindowsFirewall] section of my WINNT.SIF In the snippet below, I'm attempting Program.TestProgram (Notepad) works fine. Java (C:\Program Files\Marimba\Castanet Tuner\lib\jre\bin\java.exe) doesn't. I've experimented with placing java.exe in the correct location on the machine prior to firewall setup by placing it in $Progs...bin\java.exe, but still no joy. Any suggestions as to why I can't get java.exe working either way I try it? I'm sure I'm just overlooking something dumb, so I thought I'd step away a few feet from it and let you guys look at it. [WindowsFirewall] Profiles=WindowsFirewall.Standard LogFile = "%WINDIR%\pfirewall.log" LogSize = 4096 LogDroppedPackets = 0 LogConnections = 1 [WindowsFirewall.Standard] Type = 3 Mode = 1 Exceptions = 1 Notifications = 0 MulticastBroadcastResponse = 1 AllowedPrograms = WindowsFirewall.Java, WindowsFirewall.Java2, WindowsFirewall.TestProgram Services = PortOpenings = WindowsFirewall.Marimba, WindowsFirewall.MarimbaTL, WindowsFirewall.Dameware, WindowsFirewall.EPO1, WindowsFirewall.EPO2, WindowsFirewall.EPO3 IcmpSettings = WindowsFirewall.EchoRequest [WindowsFirewall.Java] Program = C:\Progra~1\Marimba\Castan~1\lib\jre\bin\java.exe Name = Java Mode = 1 Scope = 0 [WindowsFirewall.TestProgram] Program = %systemroot%\notepad.exe Name = TestProgram Mode = 1 Scope = 0 [WindowsFirewall.Java2] Program = "C:\Program Files\Marimba\Castanet Tuner\lib\jre\bin\java.exe" Name = Java2 Mode = 1 Scope = 0 [WindowsFirewall.Marimba] Protocol= 6 Port = 7717 Name = Marimba Mode = 1 Scope = 0 [WindowsFirewall.MarimbaTL] Protocol= 6 Port = 8080 Name = Marimba_Tuner_Logger Mode = 1 Scope = 0 [WindowsFirewall.Dameware] Protocol= 6 Port = 6129 Name = Dameware Mode = 1 Scope = 0 [WindowsFirewall.EPO1] Protocol= 18 Port = 8082 Name = ePO_Super_Agent Mode = 1 Scope = 0 [WindowsFirewall.EPO2] Protocol= 18 Port = 49441 Name = ePO_Wakeup Mode = 1 Scope = 0 [WindowsFirewall.EPO3] Protocol= 18 Port = 49339 Name = ePO_Communications Mode = 1 Scope = 0 [WindowsFirewall.EchoRequest] Type = 8 Mode = 1

I enjoy Advanced Registry Tracer.

I go a bit further when making my builds. Since I like to keep at least a version numbering scheme, I have a small Kix script incriment the build number on my CD-Menu, and make sure the OEMDuplicatorString gets it too for my eventual Sysprep process. (My auto-disc is different, in that I do a full install, and then sysprep the machine -- it's used for getting new hardware into our environment, making sure nobody builds a machine that isn't exactly like the other ones we have.) I use the Kixscripts editor to make a nice EXE out of it. It incriments my build number, asks me if I want to upgrade my version numbers, and then makes the DVD that I use in VMWare for testing. ;=============================================================================================== ;***** Created with KiXscripts Editor | http://KiXscripts.com ***** ;***** Last Modified on 1/5/2005 at 2:48:19 PM by REMOVED ***** ;=============================================================================================== ; Version Updater ? ? ? ? $rc=MessageBox("Incriment Major","AutoBuild",292) ; Yes Button Returns 6 ; No Button Returns 7 If @error=6 $IncrimentMajor=1 Else $IncrimentMajor=0 EndIf $rc=MessageBox("Incriment Minor","AutoBuild",292) ; Yes Button Returns 6 ; No Button Returns 7 If @error=6 $IncrimentMinor=1 Else $IncrimentMinor=0 EndIf Break on Del "C:\Documents and Settings\REMOVED\Desktop\Tree-2\boot\cdshell.new" $rc=Open (1,"C:\Documents and Settings\REMOVED\Desktop\Tree-2\boot\cdshell.ini",2) $rc=Open (2,"C:\Documents and Settings\REMOVED\Desktop\Tree-2\boot\cdshell.new",5) $CDShellLine=ReadLine(1) While NOT @ERROR If InStr($CDShellLine,"Unattended Boot DVD") ;Get the Build Number $VerLen=Len("$CDShellLine") $VerRight=Right("$CDShellLine",$VerLen-37) $VerRightLen=Len($VerRight) $VerLong=Left("$VerRight",$VerRightLen-11) $VerIndividual=Split($VerLong,".") ; Possibly Incriment Major If $IncrimentMajor=1 $VerIndividual[1]=(Val($VerIndividual[1])+1) EndIf ; Possibly Incriment Minor If $IncrimentMinor=1 $VerIndividual[2]=(Val($VerIndividual[2])+1) EndIf ; Auto Incriment the Build Number $VerIndividual[3]=(Val($VerIndividual[3])+1) $CDShellLine= 'print c " == \cXXUnattended Boot DVD '+$VerIndividual[0]+'.'+$VerIndividual[1]+'.'+$VerIndividual[2]+'.'+$VerIndividual[3]+'\cxx == \n"' EndIf $rc=WriteLine (2,$CDShellLine+@CRLF) $CDShellLine=ReadLine(1) Loop $rc=Close(1) $rc=Close(2) Del "C:\Documents and Settings\REMOVED\Desktop\Tree-2\boot\cdshell.ini" Copy "C:\Documents and Settings\REMOVED\Desktop\Tree-2\boot\cdshell.new" "C:\Documents and Settings\REMOVED\Desktop\Tree-2\boot\cdshell.ini" ; Upate the OEM Builder String $rc=SetOption('NoVarsInStrings','On') $rc=WriteProfileString('C:\Documents and Settings\REMOVED\Desktop\Tree-2\$OEM$$\$1\Sysprep\sysprep.inf',"GuiUnattended","OEMDuplicatorstring","Auto XP Build "+$VerIndividual[0]+'.'+$VerIndividual[1]+'.'+$VerIndividual[2]+'.'+$VerIndividual[3]+' - mstenge@@chw.edu') $rc=SetOption('NoVarsInStrings','Off') ? ? 'Old Version Was : '$Verlong ? 'New Version is : '+$VerIndividual[0]+'.'+$VerIndividual[1]+'.'+$VerIndividual[2]+'.'+$VerIndividual[3] ? ? 'Building Multi-Boot ISO' ? ? Shell ('"C:\Program Files\nLite\data\makeiso.exe" -volid "CHWXP" -allow-multidot -relaxed-filenames -allow-leading-dots -N -l -d -D -joliet-long -duplicates-once -b boot/loader.bin -no-emul-boot -boot-load-size 4 -o "d:\XPUSP2-2.ISO" "C:\Documents and Settings\REMOVED\Desktop\Tree-2" ') $rc=MessageBox("Make Non-MultiBoot ISO?","AutoBuild",276) ; Yes Button Returns 6 ; No Button Returns 7 If @error=6 Shell ('"C:\Program Files\nLite\data\makeiso.exe" -volid "CHWXP" -allow-multidot -relaxed-filenames -allow-leading-dots -N -l -d -D -joliet-long -duplicates-once -no-emul-boot -b boot.bin -hide boot.bin -hide boot.catalog -gui -o "d:\XPUSP2.ISO" "C:\Documents and Settings\REMOVED\Desktop\Tree-2"') EndIf Sleep 2 Excuse some of the lazy Kix coding, I was in a hurry.

So that I'm clear, you're logging on as Admin, then, as a portion of your as-admin setup, you're calling a registry import that changes the autologon information to the next user that you want to logon as and process information. You're saying your auto-logon registry import setting (a) don't get into the registry, or are (B) ignored. What happens when you perform this manually? Can you isolate the problem to one with your script, or one TRULY with the machine ignoring your changes. If you're just logging off, it won't re-auto-logon. You'll have to at least reboot. Logoff won't generate an auto-logon (off the top of my head, too lazy to look in VMWare at the moment.)

You are absolutely right.... but this is the only way for now. I also hate these binary tweaks... but if you want to modify the corresponding hexadecimals, you'd have to indentify them first (that may not be a big problem) but you'd have to find a way of modifying them properly. Also... you don't want to know what happens to this registry-entry if you add a toolbar to the taskbar. (For example, I add a directory: %SystemDrive%\Tools). The data almost doubles!! Try to monitor then what exactly happens... Oh, I have. When you add a toolbar, a counter to identify the NUMBER of items increases, and then the information about that toolbar is appended (or inserted) into the data. (I've looked at a lot of before/after snapshots with Advanced Registry Tracer.) Identifying the format is important. If I knew the format, I'd make a tool that read it, parsed it and spat it back out. Screw it, I'm *going* to decypher the damned thing.

nLite just shells to msisofs with a command line much like... mkisofs -iso-level 4 -l -d -D -J -joliet-long -b YOURBOOTBIN.BIN -hide boot.catalog -allow-multidot -no-emul-boot -volid "YOURVOLID" -boot-load-size 4 -o "YOUR ISO FILE.ISO" "YOUR SOURCE DIRECTORY" (Edit: And include -duplicates-once if you want to have it save multiple references to the same file as single files -- you know, for making AIO discs, saving space, etc.)

While I'm being a grumpy guy today, I'll ask again, why are we suggesting both /passive and /quiet on the command-line for the new "we got bored and changed the command-line again" patches. /passive doesn't WANT /quiet to be non-interactive. /quiet doesn't NEED /passive to be silent.

I don't doubt that the fix works. I know it does. I understand that at and before T-12 stage changes to the HKCU tree get applied to the default profile. I'm saying that the current method, of importing a mostly clean changed registry key is a massive kludge. We know that that the \Streams\Desktop\TaskbarWinXP key holds some basic information. It holds a value for the number of items on the taskbar, and then a description of those items. It is incorrect to label this as the "Add Quicklaunch" key. This is a "Make your taskbar look exactly like this one, that happens to includes Quicklaunch." My question wasn't so much of a "how do I do this," but more of an "has anyone looked into doing this the RIGHT way." Hundreds of people having done it before with a kludge doesn't make it any less of a kludge, and it's hardly deserving of a RTFM answer. So, I'll ask again, has anyone done any more work in taking this apart than the people who identified the byte that holds the number of entries (the 8th, I believe, without checking the other thread). I understand that, because of the way this key works, there will never simply be a registry add that does this the RIGHT way. You'll always have to read the key, perform an analysis of it, and then write it back. You can argue, of course, that what the current change does produces the same result - but forgive me for wanting to make it work... ...right.

Like other users, I'm pretty sure this is the "wrong" way to go about forcing the QuickLaunch toolbar: ;----- Enable Quick Launch ;----- [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Streams\Desktop] "TaskbarWinXP" Before I waste my evening trying to figure out exactly how that giant bitmapped field works, and make a small script to flip the right bits, if anyone knows the REAL answer, I'd apprecaite it.

The non-administratively available Outlook View Control SR-1 update was the culprit as stated in the first article I linked. Thanks anyway. http://support.microsoft.com/?kbid=303833 Relevant Portion of the Article:

Similar problems are reported here, but this doesn't appear to be my problem: http://www.mcse.ms/message526646.html And another http://groups-beta.google.com/group/micros...67c10126d86913b

Nope. SP3 for Office 2000 is for SP1 and replaces SP2. You can't do a no-SP to SP3 upgrade. My administrative install point is correctly built from the "prescribed" method. SP1a media from Licensing.Microsoft.COM, updated with SP3 from /downloads, then all post-SP3 administrative transforms applied manually with msiexec /p. All products show as SP3, and all post-SP3 patches show as installed. Only OfficeUpdate is fooled.

I've researched this problem here and by google (of course), but I'm running only into other people showing the same problem. I have an administrative install point for Office 2000. It was originally SP1, and was correct patched to SP3 with all post-SP3 patches. OfficeUpdate correctly identifies all the post-SP3 patches, but shows that I need SP3. [i do not need SP3, it's just an error through OfficeUpdate.] I've read a few times that this is the fault of bad settings in the SETUP.INI, but, frankly, there aren't settings in my SETUP.INI Suggestions? Similar experiences?