fragbert
Content Type
Profiles
Forums
Events
Posts posted by fragbert
-
-
I have made a post about this last year to which there was no resolution: http://www.msfn.org/board/Dreaded-framedyn...ml&p=646947
After starting from scratch with an untouched, freshly downloaded MSDN XP VLK w/ SP3 already integrated, I have irrefutable proof that nlite breaks the install. No other tools, addons or anything else used; I simply add a series of tweaks in the "tweaks section" and what results at the end of the install is the framedyn.dll error and messed-up icons:
Now, if I select the "options" section of nlite (make it green) but do not actually make any changes in that section, nlite processes the same as above yet I DO NOT get the problem! There is some kind of processing done in nlite that severely messes up my VLK (be it MSND SP3 or XP RTM) if I don't select the options tab. I suspect that this bug is specific to VLK images since so many other people do not have issue.
I was reminded of this problem when onpiece made an addon that defeated an XP SP3 integration bug and no longer required to disable SFC to get working. So I went ahead and unselected the options tab in nlite (where SFC enable/disable is located) and ran an install and saw the bug creep up. Now, OF COURSE, my further testing to replicate this bug involved NO other tools or addons whatsoever. Just a naked MSDN XP VLK ISO, nlite, and an install in VirtualPC 2007.
0 -
I ran nlite 1.45 final to just add a few explorer tweaks, nothing more, and the last session.ini has a bunch of settings that I did not set, including what looks like removal of trivial files and setting some unattended stuff. Is this normal behavior?
This is all I wanted nlite to do:
[Tweaks]
Boot and Shutdown-Auto-Kill hung applications immediately
Boot and Shutdown-Status Messages-Extended
Explorer-Add 'Command Prompt' to folder context menu
Explorer-Change Windows Explorer folder view-List
Explorer-Classic Control Panel
Explorer-Disable Search Assistant
Explorer-Launch folder windows in a separate process
Explorer-Show extensions of known file-types
Explorer-Show Statusbar in all windows
Performance-Minimal Power Management
Performance-Use Windows classic folders / No Tasks Sidepanel
Start Menu-Control Panel-Don't display this item
Start Menu-My Documents-Display as a menu
Start Menu-My Music-Don't display this item
Start Menu-My Network Places-Don't display this item
Start Menu-My Pictures-Don't display this item
Start Menu-Network Connections-Don't display this item
Taskbar-Disable Language-Bar
Taskbar-Disable Windows Tour popup
Taskbar-Lock the Taskbar-Yes
Yet it does ALL of this:
[Tasks]
Tweaks
[Components]
;# Compatibility #
[KeepFiles]
msconfig.exe
[RemoveFiles]
clock.avi
yahoo.bmp
swtchbrd.bmp
[Options]
ProfilesDir = "%SystemDrive%\Documents and Settings"
TargetPath = "WINDOWS"
temp_dir = %USERPROFILE%\Local Settings\Temp
AdvTweaks
[unattended]
ComputerType = Automatic
MaximumDataStorePercentOfDisk = 12
RestorePointLife = 30
DesktopTheme = Default||
AutoUDay = 5
AutoUHour = 15
ProgFilesPath = "\Program Files"
[NetAdapter1]
connname = ""
macaddress = ""
ipaddress = "192.168.0.1"
subnetmask = "255.255.255.0"
defaultgateway = ""
dnsserver1 = ""
dnsserver2 = ""
winsserver = ""
netbiossetting = "0"
ipxnetworknumber = "00000000"
ipxnetworkframetype = "0xFF"
0 -
Nothing? Any idea where this question might get an answer? Still stuck here
0 -
I'm having the strangest problem with a particular computer running my standard unattended XP SP2 setup (a setup that has been used trillions of times on every kind of PC without any problems), it's your basic latest RVM + latest driverpacks + latest essential addons (IE7, adobe, etc).
Anyways the problem is that for whatever reason, storprop.dll is not copied from the driver.cab to system32 on this particular PC and thus I get those silly device installer errors for all my storage devices (CDROM, harddisk) and asks to install a driver that it will never find. I say "silly" because the hardware works fine and is accessible from XP. Manually copying storprop.dll from driver.cab in the driver cache folder solves the problem instantly (after telling the device manager to scan for new hardware).
Troubled PC specs:
E8400
DX38BT
2GB DDR3
1TB RAID1 (2 samsung 1TB's)
Radeon 3870
LiteOn 20X DVD+/-R
I have verified this very same unattended XP install image on several other PCs, all very similar to the troubled one (q35 and Q965 based intel boards with integrated graphics and AHCI or RAID mode) and installs without issue - AND - storprop.dll is where it should be in system32.
Could this stem from hardware? I figure it has to be since the install source is verified to work on everything else. Perhaps this X38 chipset has some BIOS settings I'm overlooking, or this LiteOn is being a pain and for whatever reason blocking the storprop.dll from copying.
0 -
Nevermind, 10.3.0.24 will install from adobe.com, even though their download page states it's 10.2
0 -
v10.3.0.24 just got pushed out via Adobe's autoupdate system. Still not on their website as a separate download.
0 -
Referencing the latest WGAN, direct link here: http://www.download.windowsupdate.com/msdo...da5cec6c0d4.exe
The downloaded hotfix package seems to not integrate properly - or at least does not shut up Microsoft Update or Automatic Updates. Using /passive from RunOnceEX seems to work fine, reboots, and presto....AU starts nagging about installing it again! In fact, running the downloaded executable manually yields the same results as well. AU will only shut up once it installs the update from AU.
Any ideas?
0 -
Thanks fragbert!
Somebody found how to slipstream KB936677? Or fragbert and me are the only two with this problem?
And here's another issue - when running this hotfix to install from RunOnceEx, it does not register somehow and both Microsoft Update and Office Update will state that it needs to be downloaded.
0 -
Same problem here (Office 2003 Pro ITA)! KB936677 doesn't slipstream!
I read that you could slipstream SP3 and install Office 2003 SP3 without any problem with your MST. I'm trying also to do it, but I'm not able: can you explain me how to do it? Thanks!
0 -
Just made a fresh admin install point for Office 2003 and slipstreamed Service Pack 3. No problems, installs perfectly with my MST.
BUT
The only update post SP3, the latest 09/07 edition of the Outlook junk mail filter http://support.microsoft.com/kb/936677/ will not slipstream into my source. MSIEXEC gives an error when trying to slipstream the MSP.
Anybody else have this problem or just me?
Using standard command line that I've used with zero problems integrating sp2 hotfixes in the past: msiexec /p [hotfix].msp /a [admin install source directory]\pro11.msi SHORTFILENAMES=TRUE /qb
0 -
boooggy,
I'm trying to integrate WMP11 in to the clean sources of WinXP SP2 Corp using Windows Media Player 11 Slipstreamer 0.71 and have an error:
System.InvalidOperationException: The section "ProductInstall.ReplaceFilesIfExist" does not exist!â System.Text.Ini.SimpleIniEditor.ThrowNotFoundSection(String SectionName)â System.Text.Ini.SimpleIniEditor._internalReadMethod(String Section, String Key, Boolean FirstInstanceOnly)â WMP11Slipstreamer.Backend.CompressFiles()â WMP11Slipstreamer.MainGUI.workerMethod(Object addonSettings)Deleting "G:\VRMPVOL_RU\i386\wmp11temp"... Done!The source being modified has not been damaged.All changes have been successfully reverted.I'm using all official fix's for WMP11 from this page.
Seems what en error caused last fix - KB935957.
Ditto for me too with 0.72 and that hotfix. So we should not use this hotfix? When you say "not really needed", does that mean you do the reg mod yourself?
0 -
RyanVM has nothing to do with my problem, as I clearly stated the issue manifests when using original VLK XP media if I manually integrate SP2 beforehand vs using Nlite to integrate the service pack. What fixes the issue is to select the options tab but dont actually change anything and Nlite will go through a "processing files" stage. No clue on what it is actually processing but that prevents the .dll errors if I chose to utilize any tweaks.
I am aware of how you get this issue, the point I was making is that I am getting exactly the same errors without doing anything to SP2, manually or otherwise because my media has SP2 already in it.
Anyway, after dropping back to the earlier edition of Ryans pack I still get this error so it is not the pack itself and must be an addon that I am using. My tweaks section is identical to the earlier working ones. In fact my whole nLite section is identical to eariler, successful builds so I am more puzzled now than ever.
Maybe it's the current version of nLite we are using? Try not using any addons whatsoever and just use your tweaks. If that gets the error, see if you can revert back to an earlier version of nlite.
0 -
-
RyanVM has nothing to do with my problem, as I clearly stated the issue manifests when using original VLK XP media if I manually integrate SP2 beforehand vs using Nlite to integrate the service pack. What fixes the issue is to select the options tab but dont actually change anything and Nlite will go through a "processing files" stage. No clue on what it is actually processing but that prevents the .dll errors if I chose to utilize any tweaks.
Just to add to this further it is beginning to look like a problem with compatibility with nLite and Ryans update pack. Each works perfectly OK on its own but the issue comes when using Signet's Integrator and nLite, but only since the new pack came out - never had an issue with the March update pack or any before that.I normally use the Integrator to add the latest update pack then nLite the resulting folder to reduce its size and apply a load of tweaks - the same basic setup I have used for over a year. Then I add any other addons that I need using the Integrator again before making the ISO with nLite when I am finished.
If I just add the update pack with the integrator and just run nLite with no additonal addons it works. Add even a single addon and the install breaks - even with addons that I have used for a long time so know that they are fine.
As a final check I just finished running the whole lot in nLite alone with no integrator involved and got the same failure - so the only common factor is the new update pack.
Going to try dropping back to the March pack and try it again and if the errors go away it sort of proves where the problem then lays.
0 -
After messing around with nlite, I discovered some new commands that apparently can be added to XP's WINNT.SIF that can disable SystemRestore:
[systemRestore]
DisableSR=1
CreateFirstRunRp=0
However I can not get this to work for me. Upon installing my UWXP image, SystemRestore is still enabled. Can anybody here verify that this does indeed work? Is placement within the WINNT.SIF important?
0 -
-
After messing around with nlite, I discovered some new commands that apparently can be added to XP's WINNT.SIF that can disable SystemRestore:
[systemRestore]
DisableSR=1
CreateFirstRunRp=0
However I can not get this to work for me. Upon installing my UWXP image, SystemRestore is still enabled. Can anybody here verify that this does indeed work? Is placement within the WINNT.SIF important?
0 -
I have been having this problem (among other things missing) for some time now, and searching the forum only revealed other people having the same problem, lots of advice and ideas - but no solution.
In my case, I also just have slipstreamed SP2 into a copy of my original medium. Then I use nLite to integrate the hotfixes, nothing more. Still, it seems nLite removes the dll (and logoff.exe) for some reason. I even tried to just select hotfix integration but not actually add any hotfix - same result.
Currently, I am experimenting with simply adding framedyn.dll to the keep list (along with logoff.exe), but it's beyond me why that should be necessary in the first place if I don't do any space-optimization.
Glad to see I am not alone here
What is very strange is that I can avoid this problem by either integrating SP2 using Nlite - or if I had manually integrated SP2 beforehand, I select the options tab but dont actually change anything and Nlite will go through a "processing files" stage. No clue on what it is actually processing but that prevents the .dll errors if I chose to utilize any tweaks.
0 -
did you download a fresh sp2 installer from MSFT?
Yes. Not that it matters, if it was remotely corrupt it would not install due to a hash failure.
UPDATE: And I get the DLL errors on a naked XP RTM (no service packs), the original VLK media sent directly from MS - again after applying just one tweak.
0 -
Recopy from the original CD, or ISO and use only nLite on it, don't do anything manually nor with some other tool just to see does it break.
Also if it breaks again on only tweaks then try not even tweaks, just create ISO and see if that fails.
Of course use virtual machines for this, no need to spend CDs or mess with your real partitions.
OK here is what happened:
Integrate SP2 to my original VLK XP CD using Nlite - no problems applying anything else afterwards.
Manually integrate SP2 first using sp2.exe s:<source>, then use nlite to apply one single tweak (command prompt from explorer) - .dll errors.
Manually integrate SP2 using above method, then use nlite to apply said tweak AND adding an option (TCPIP connects to 100) - no problems.
Any ideas?
0 -
Tested your preset and it went fine.
That error tells me that some other modification tampered with system files and haven't patched what needed to be patched.
If you want to easily solve that try to either remove one component with nlite or use one of the patches in the Options page then nLite will take care of the patching.
Just to be clear I strongly believe that nLite on it's own isn't responsible for the error. If you are again sure in otherwise then please try to be more specific how to get that error because only preset didn't do it.
I don't rule out the possibilty that my "clean" XP SP2 source may have been inadvertently modded or tampered - the trouble is were to look?
I followed your instructions by removing one component (games) and also used an option patch (TCPIP to 100 connections), and this time no error! Ok this is a good step in the right direction, what next?
Thanks!
0 -
Edited to reflect general problem without updatepacks.
0 -
UPDATE: I get these same errors using nlite on an untouched XP SP2 installation source! Same source I've been using for about two years now. This is without any driverpacks or updatepacks whatsoever. Yikes!
Hi, I am at odds with the Tweaks section of Nlite.
For a span of about a year I have been fortunate enough to have success with combining nlite, ryanvm's update pack integration, and BTS's driver packs for my unattended XP installations. My dealings with nlite were strictly in the Setup portion (Unattended, Options, and Tweaks tabs). However since the last few update packs, I have not been able to get nlite and ryanvm's packs to play nice - and ONLY if I use the tweaks section. I use a few explorer, start menu, task bar, and comand prompt tweaks - that's it (no "red" advanced tweaks either). What results is the dreaded framedyn.dll and srclient.dll errors along with a messed up start menu and IE icon replaced with the internet setttings cpl.
I'm so used to the minor explorer/startmenu/taskbar tweaks from nlite, it will be hard to give up, but unfortunately for me the ryanvm update pack is more important for now. I am wondering if any of you have an alternative method/program for adding these tweaks to an unattended install source? Maybe a simple .reg from RunOnceEx?
Of course I'm open to diagnosing the problem but I don't think that will go far...
Here is my Last Session.ini
[Main]
Env = 1.3 - 2.0.50727.42.Microsoft Windows NT 5.1.2600 Service Pack 2
Target = Windows XP Professional SP:2 - 5.1.2600.2180 - English (United States)
[Tasks]
Tweaks
[Components]
;# Compatibility #
[KeepFiles]
msconfig.exe
[RemoveFiles]
clock.avi
yahoo.bmp
swtchbrd.bmp
[Options]
ProfilesDir = "%SystemDrive%\Documents and Settings"
TargetPath = "WINDOWS"
temp_dir = %USERPROFILE%\Local Settings\Temp
AdvTweaks
[Patches]
[Services2]
[Tweaks]
Explorer-Add 'Command Prompt' to folder context menu
Explorer-Advanced Search: preconfigure options
Explorer-Classic Control Panel
Explorer-Disable Search Assistant
Explorer-Display the contents of system folders
Explorer-Launch folder windows in a seperate process
Explorer-Show Drive Letters in front of Drive Names
Explorer-Show extensions of known file-types
Explorer-Show hidden files and folders
Explorer-Show protected operating system files
Explorer-Show Statusbar in all windows
Explorer-Show the full path in the Address Bar
Explorer-Use small icons in Explorer bar
Performance-Minimal Power Management
Performance-Use Windows classic folders / No Tasks Sidepanel
Security-Screensaver Password-Protection-Enabled
Start Menu-Add Administrative Tools menu
Start Menu-Control Panel-Display as a menu
Start Menu-My Documents-Display as a menu
Start Menu-My Music-Don't display this item
Start Menu-My Network Places-Don't display this item
Start Menu-My Pictures-Don't display this item
Start Menu-Network Connections-Don't display this item
Start Menu-Reduce popup delay
Start Menu-Remove Set Program Access and Defaults
Start Menu-Remove Windows Catalog shortcut
Start Menu-Remove Windows Update shortcut
Start Menu-Show IE Favorites
Taskbar-Disable Hide inactive icons
Windows Media Player-Accept Privacy Statement
[Unattended]
ComputerType = Default
MaximumDataStorePercentOfDisk = 12
RestorePointLife = 30
DesktopTheme = Default||
AutoUDay = 5
AutoUHour = 15
ProgFilesPath = "\Program Files"
[NetAdapter1]
connname = ""
macaddress = ""
ipaddress = "192.168.0.1"
subnetmask = "255.255.255.0"
defaultgateway = ""
dnsserver1 = ""
dnsserver2 = ""
winsserver = ""
netbiossetting = "0"
ipxnetworknumber = "00000000"
ipxnetworkframetype = "0xFF"
[GuiRunOnce]
[Drivers]
[Hotfixes]0 -
I tried running a batch command in RunOnceEx that runs a .reg which adds these statements:
Windows Registry Editor Version 5.00
[HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server]
"fDenyTSConnections"=dword:00000000
If I run this batch file from the desktop, it works. Running from unattended install in RunOnceEx does not. Strange.
0
Did an update reset XP firewall settings to default?
in Windows XP
Posted
Every so often after a patch tuesday, I have XP workstations that all of the sudden drop all the allowed applications in the XP firewall (including file and print sharing, VNC, etc) and really puts me in a bind because I no longer have remote access to these machines until I manually put VNC back on the allowed list.
What gives? This affects machines in domain and stand alone environments, and no GPO or other outside enforcement that would touch the firewall, so that's why I'm assuming it's a stupid MS update issue. What is a good method to universally insure this wont happen again (other than disabling XP firewall )