This post has been edited by davgkill: 11 June 2008 - 10:58 PM
nLite 1.4.9.1 - Honey Turbo 9.1 Remove components. Unattended. Integrate drivers, hotfixes, themes...
#201
Posted 11 June 2008 - 10:56 PM
#202
Posted 12 June 2008 - 07:24 AM
#203
Posted 12 June 2008 - 07:41 AM
AgiHammerklau, on Jun 7 2008, 05:38 AM, said:
I know the answer !
It´s e) !
You´re here as long as me.
So some basic stuff seems to slip from the memory due to habits.
NEVER EVER USE A PRESET, THAT HAS BEEN CREATED WITH A FORMER VERSION !
Even the slightest x.x.2 update makes your former presets unreliable or even completely fails it.
It´s in the "sticky" !
Agi
Never! Not true! You can always use old preset with new version. Only when Nuhi points out that old preset don't work then you should not use it. I always use my same presets with new version and I haven't a single problem. Also there is no "sticky" with this.
Cheers
#204
Posted 12 June 2008 - 08:06 AM
I am installing via network using a boot floppy (as my subnotebooks do not have an optical drive) - so I have to use the winnt.exe for setup.
All worked fine with several addons integrated with nlite until sp2. With sp3 (already integrated by microsoft ISO used) all the symptoms occur.
Is there currently no way to prepare nlite on being used using the winnt.exe method or did I read wrong?
Thanx for ur reply
Pat
#205
Posted 12 June 2008 - 08:18 AM
Well try 1.4.6.
#206
Posted 12 June 2008 - 09:43 AM
Manual removing of the 5 mof/mfl files in txtsetup.sif ruled, so i could install my nlited winxpsp3 with working addons.
I will give it a try without modification using nlite 146 these days - only waiting for sereby to repack for june patches.
One problem is left (using the manual method):
Using nlite on 2005 tablet edition sp3 results in the on screen keyboard in being blank inside. Again it worked with sp2 tablet edition without problems. Also after having used nlite I am requested to provide a sprseng.dll (from microsoft) that is not requested when installing vanilla tablet pc edition with sp3 integrated...
#208
Posted 12 June 2008 - 12:18 PM
#209
Posted 12 June 2008 - 12:56 PM
davgkill, on Jun 11 2008, 11:56 PM, said:
This sounds similar to the issue I'm running into:
Initial attempt:
http://www.msfn.org/board/index.php?s=&...st&p=768481
Godan's suggestion:
http://www.msfn.org/board/index.php?s=&...st&p=768505
My results:
http://www.msfn.org/board/index.php?s=&...st&p=772190
#210
Posted 12 June 2008 - 07:41 PM
I have a Windows XP HOME sp1 HUN install disc. I integrate sp3 with nlite, but it wont accept the serial. What's wrong?
When i integrate sp2, the serial worked!
#211
Posted 13 June 2008 - 02:29 AM
#212
Posted 13 June 2008 - 04:13 AM
Octopuss, on Jun 12 2008, 08:18 PM, said:
Did you even try to read my previous post here? No, you don't need to redo your preset when new version is out, you can always use the same!
mm00, on Jun 13 2008, 03:41 AM, said:
I have a Windows XP HOME sp1 HUN install disc. I integrate sp3 with nlite, but it wont accept the serial. What's wrong?
When i integrate sp2, the serial worked!
Which version of nLite are you using? Try with latest version if don't have it. And if still does not work, I suppose you are doing slipstream under Vista. Although nLite should fix this problem, for someone fix does not work, so you'll have to slipstream under XP as host, or try to run nLite in compatibility mode in Vista.
RssRss, on Jun 13 2008, 10:29 AM, said:
First, upgrade your nLite to latest version. Second, upload your preset. Third, try to create ISO with nLite and to burn it with some burning software and use lower speed when burning.
Cheers
This post has been edited by mara-: 13 June 2008 - 04:14 AM
#213
Posted 13 June 2008 - 02:04 PM
Quote
Be glad, that it always (!) works for you.
For me and several others, it doesn´t.
I was talking about final versions.
(But even some tweaks in a (silent) update -and you are correct, Nuhi explicitely notifies us- can make an older preset unreliable, not to mention, what happens, if the drivers or addons are not in the same path anymore.
It was in the "sticky"-thread of an older final.
E.g. there were several problems due to the (german) languagefile-update in the "german-nlite.de"-forum.
(But now everybody is happy about it)
Don´t know, if there have been similar problems in other fora.
Even if we´re talking about "non-localized" english versions of windows, I still doubt, that a preset, built with a former final, is working flawless on an actual one.
So it is "ill-advice" to say :
"It always (!) works, unless we´re notified by Nuhi".
You wouldn´t import an old 1.2.1 preset yourself, won´t you ?
@all
Use the presets, built within the same final-version, unless it´s specifically mentioned othervise (have a look in the changelogs) and you´re on the safe side.
Agi
This post has been edited by AgiHammerklau: 13 June 2008 - 02:06 PM
#214
Posted 14 June 2008 - 03:36 AM
Wonder how that happened!
#215
Posted 14 June 2008 - 11:40 AM
#216
Posted 14 June 2008 - 06:03 PM
GrofLuigi, on Jun 7 2008, 04:15 AM, said:
Boot and Shutdown-Setup Prefetch-Cache-Disabled
Explorer-Disable Accessibility keyboard shortcuts
Explorer-Launch folder windows in a seperate process
Performance-Enable USB Idle Endpoint support
Start Menu-Disable popup on first boot
Visual Effects-Smooth edges of screen fonts-ClearType
Windows Media Player-Disable silent acqusition
While working with nLite, I didn't check specifically for these items, but everything seemed fine, just the way I always do it. Are these tweaks:
a ) removed from nLite?
b ) removed from XP SP3? (the previous preset MIGHT have been from SP2)
c ) moved to another place in nLite? (but there were no new entries similar to them)
d ) a bug in nLite? (forgot them)?
e ) my mistake? (should've started from scratch, but then why have Import Last Session Ini anyway?)
This was checked by doing text compare of the Old Preset.ini and Last Session.ini. When I install the CD, I will know more, but sometimes some of the tweaks don't 'take', so...
Which letter is it?
GL
After install, it seems that the tweaks were applied. Can't know for sure because I don't know the exact location for some of them. But I don't understand why were they removed from Last Session.ini.
Again, what I did was:
- Load nLite
- Import Old Session.ini which I work with most of the time
- Adjust some settings (not the ones above, I usually don't touch them; maybe only USB idle)
- make ISO and finish nLite
- binary compare Old Session.ini and Last Session.ini - they are not present
- but they are applied?!
Now I don't understand anything. I guess it isn't a bug, it's a feature - only Nuhi can tell.
Off to building New Session.ini.
GL
#217
Posted 16 June 2008 - 12:55 AM
(unless someone tells me how /if/ do I run another instance of nLite on same PC..
#218
Posted 16 June 2008 - 07:28 AM
I gave 1.4.6 a try. It comments the nap*.mof in wbemoc.inf, but errors/broken installs are not gone using the winnt.exe method via share.
Currently it is necessary to do the following steps:
Mit nlite 1.4.6
ISO with sp3 integrated (vanilla ms)
Run Nlite and import last.exssion.ini
add addon packs (i take sereby's german ones for fixes, runtimes, wmp11 and ie7), ie7 addon at last
txtsetup.sif:
acadproc.dll doppelte Einträge weg (remove duplicate entry)
napprov.mof, napschem.mof, rsop.mof, wscenter.mof, and rsop.mfl --> remove or comment ;.
unpack wbemoc.in_ and remove/comment above 5 files in [WBEM.CopyMOFs]
replace usetup.exe in the I386 with SMSS.exe from I386\System32
add $$replace file in $oem$/$1/system32:
[\WINDOWS\System32\WBEM] evtgprov.dll = "CmdEvTgProv.dll" evtgprov.mof = "CmdEvTgProv.mof" Napprov.mof = "NapClientProv.mof" NapSchem.mof = "napclientschema.mof" [\WINDOWS\System32\] msjetol1.dll = "msjetoledb40.dll" class_ss.dll = "shellstyle.dll"
(Optional) recompress with makecab: svcpack.inf und wbemoc.inf, and remove unpacked files.
delete lang und win9xmig dirs
My last session.ini for information:
[Main] Env = 1.4.6 - 2.0.50727.1433.Microsoft Windows NT 5.1.2600 Service Pack 3 Target = Windows XP Professional SP3 - 5.1.2600.5512 - Deutsch (Deutschland) [Tasks] Remove Components Hotfixes and Update Packs Tweaks Options [Components] ;# Anwendungen # Ablagemappe Aktentasche Bildschirmschoner Eingabehilfen Internet-Spiele Paint Pinball Spiele ;# Betriebssystem # Blaster/Nachi-Entfernungswerkzeug Desktopbereinigungsassistent Dokumenten-Templates DR Watson Farbschemata Sicherheitscenter Suchassistent Tour Übertragen von Dateien und Einstellungen ;# Dienste # Fehlerberichterstattung Nachrichtendienst Netzwerkzugriffsschutz (NAP) Systemwiederherstellung ;# Hardware-Unterstützung # Brother-Geräte Gravis Digitaler Spiele-Port Iomega Zip-Laufwerk Serielle Multi-Port-Karten Teletext-Codec ;# Multimedia # AOL ART-Dateiformat Bilder und Hintergründe Luna-Theme Movie Maker Musik-Beispiele ;# Netzwerk # MSN Explorer Netmeeting Windows Messenger ;# Treiber # Grafikkarten (alte) Logitech WingMan Sony Jog Dial Toshiba DVD Decoder-Karte Treiber für Kamera und Camcorder ;# Zusätzliche Ordner # DOCS VALUEADD ;# Kompatibilität # [KeepFiles] msconfig.exe [RemoveFiles] clock.avi yahoo.bmp swtchbrd.bmp [Options] ClassicSetup ProfilesDir = "%SystemDrive%\Dokumente und Einstellungen" TargetPath = "WINDOWS" temp_dir = %USERPROFILE%\Lokale Einstellungen\Temp [Patches] [Services2] [Tweaks] Arbeitsplatz-Entfernt 'Gemeinsame Dokumente' Arbeitsplatz-Fügt 'Verwaltung' hinzu Explorer-Erweiterte Suchoptionen voreinstellen Explorer-Inhalt der Systemordner anzeigen Explorer-Klassische Systemsteuerung Explorer-Statusleiste anzeigen Explorer-Vollständigen Pfad in der Adressleiste anzeigen Explorer-Vollständigen Pfad in der Titelleiste anzeigen Explorer-Zeigt die Dateiendung bekannter Dateitypen Leistung-Herkömmliche Windowsordner verwenden Leistung-WBEM-Logging deaktivieren Privatsphäre-Alexa Spyware entfernen Privatsphäre-Aufforderung zum Treiberupdate via Internet ausschalten Startmenü-Keine 'Persönlich angepassten Menüs' verwenden Startmenü-Startmenü ohne Verzögerung öffnen Visuelle Effekte-Animation der Ein- und Ausblendung von Tasks in der Taskleiste-Deaktivieren Visuelle Effekte-Combobox-Animation-Deaktivieren Visuelle Effekte-Durchsichtigen Hintergrund für Symbolunterschriften auf dem Desktop-Deaktivieren Visuelle Effekte-Durchsichtiges Auswahlrechteck anzeigen-Deaktivieren Visuelle Effekte-Fade out selection-Deaktivieren Visuelle Effekte-Individuelles Hintergrundbild für verschiedene Ordnertypen anzeigen-Deaktivieren Visuelle Effekte-Kanten der Bildschirmschriftarten verfeinern-Deaktiviert Visuelle Effekte-Menüanimation-Deaktivieren Visuelle Effekte-Menüschatten-Deaktivieren Visuelle Effekte-Menü-Style-Normal Visuelle Effekte-Tooltip-Animation-Deaktivieren [Unattended] ComputerType = Automatisch MaximumDataStorePercentOfDisk = 12 RestorePointLife = 30 DesktopTheme = Standard|| AutoUDay = 5 AutoUHour = 15 ProgFilesPath = "\Programme" [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] C:\temp\nlite-nt-updatepacks\nlite-juni08\XP-SP3-Updatepack-3.8.6.exe C:\temp\nlite-nt-updatepacks\nlite-juni08\Runtime-Addon.7z C:\temp\nlite-nt-updatepacks\nlite-juni08\TweakUI-DE-2.1.cab C:\temp\nlite-nt-updatepacks\nlite-juni08\WMP11-Addon.7z C:\temp\nlite-nt-updatepacks\nlite-juni08\IE7-Addon.7z
#220
Posted 19 June 2008 - 02:38 AM
See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values. Parameter name: index at System.Char.IsWhiteSpace(String s, Int32 index) at . .(StringCollection& , String ) at . . () at . .() at . .WndProc(Message& ) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Loaded Assemblies ************** mscorlib Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400) CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll ---------------------------------------- nlite Assembly Version: 1.4.6.0 Win32 Version: 1.4.6.0 CodeBase: file:///C:/Program%20Files/nLite/nLite.exe ---------------------------------------- System Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- nLite Assembly Version: 1.4.6.0 Win32 Version: 1.4.6.0 CodeBase: file:///C:/Program%20Files/nLite/nLite.exe ---------------------------------------- System.Windows.Forms Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System.Drawing Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- nlgw Assembly Version: 1.1.0.0 Win32 Version: 1.4.6.0 CodeBase: file:///C:/Program%20Files/nLite/nLite.exe ---------------------------------------- MCDBNET2 Assembly Version: 1.32.0.0 Win32 Version: 1.32.0.1302 CodeBase: file:///C:/Program%20Files/nLite/MCDBNET2.DLL ---------------------------------------- msvcm80 Assembly Version: 8.0.50727.1434 Win32 Version: 8.00.50727.1434 CodeBase: file:///C:/Windows/WinSxS/x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.1434_none_d08b6002442c891f/msvcm80.dll ---------------------------------------- cablib Assembly Version: 8.1.0.0 Win32 Version: 8.1 CodeBase: file:///C:/Program%20Files/nLite/cablib.DLL ---------------------------------------- msvcm90 Assembly Version: 9.0.21022.8 Win32 Version: 9.00.21022.8 CodeBase: file:///C:/Program%20Files/nLite/msvcm90.DLL ---------------------------------------- ************** JIT Debugging ************** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: <configuration> <system.windows.forms jitDebugging="true" /> </configuration> When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box.
- ← Cannot log in as admin no matter what, not even in safe mode
- nLite
- No repair install with HP OEM XP? →



Help

Back to top









