Jump to content

ChrisKuhli

Member
  • Posts

    240
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Germany

Everything posted by ChrisKuhli

  1. Did you recognized how old this thread is?
  2. I've could have a look on the new Beta of the next major version Very nice but your suggestion(s) will be then in Vistapack 2.1 Beta *I* hope that damian666 will be in future (re-)enable support for installation patching, and then unattended
  3. Hello Tarun Damian uses TBar in his pack for the transparency of Taskbar! Chris
  4. Do you have a sample e.g. from my pack or from the Vistapack? I could upload one but onto my "cX2K" space if you wish... The image must be a little bit special for Windows 2000 and can't be in the normal format of Windows XP! If you see the original via reshacker extracted you see what i mean! EDIT: Have a look: Customized Windows 2000 Bootlogo
  5. One way: have a look into my sources I've done it like that: I took ntoskrnl.exe in the tgtsoft resource hacker. The embedded bitmaps i modified with it and saved in the patching dirs. Now i loaded in the reshacker (the one XPero uses) the files and put them into copies of the orgininal ntoskrnl file to test that. After that i build the patching as needed for my pack. Then i reverted the Kernel file and tried the patch via my pack!
  6. I need to know the differences between the shipped file from MS and what is needed to do - language indepndent!
  7. Hmm... i hope you don't mean my pack (in Windows 2000) i don't develop (with) it yet... @All: If you have no problem what my sources http://chriskuhli.de/x2k/cX2K.rar containing try a bit debugging
  8. // -- This post is reserved for special purposes, e.g. additional infos updates or announces. Read initial post as short introdution-- // * Some updates made to the first posting as correcting dead links and misspellings
  9. Using installshield maybe not so good if used on non-iso Windows (e.g. asian language) - might be reason for some unfamiliar errors as also in my package… btw although cX2K is stagnated at moment i've a good reason to push its old topic and bind it on my signature website - reason is beginning 2ize development which will be the new base for that!
  10. Hello I've installed Windows XP Media Center Edition on C: and Vista Ultimate x86 on D. Vize think the files on C:\Windows belong to Vista but that resides on D so it tries patch XP. Of course that fails fortunalety we can restore! Either Vize should detect %SysDrive%, or there is a bit more interaction needed? I hope for solution in next Beta, Chris
  11. The "bit" from me goes only if Dynaletik says ok, i think! Another thingy i've an issue… other thread.
  12. I second that nuhi makes so stable development stages But i heared about that the next release of vLite is on a good way Or, should we wait longer then Santa Claus comes
  13. BTW peyronnx, earlier days you worked together with damian666. Do you also yet? I don't know if he wants to "extend" the XP Part of his pack (to the power) of yours
  14. They're done when they are done Maybe the public beta release dates are not very far
  15. Seems the running platform for it isn't lower than Vista I consider about adding a Vista beneith the xpMCE on C: and the Evaluation install Win2K3_Ent D: Cause my processor supports 64Bit i will use the disk with them But what is more interest: Server2K8 (RC) or UltimateVista (Full License of course)
  16. Hello Any news in development stage of next release? Few days ago as we updated our mirror i saw your copy of local homepage included the new version as the download link text But thats not changed at all as also the download needs to if then Of course
  17. A few from me <value id="gbxReloadNotifier">Vize Reload Notifier</value> <value id="radioNotifierDisabled">Deaktiviert</value> <value id="radioNotifierEnabled">Aktiviert</value> <value id="lblNotifierDesc">Vize Reload Notifier informiert wenn ein Reload von Systemdateien nötig ist.</value>
  18. Aware of Win2K3 Server is mostly of course not the goal of a package like this (issues of bootscreen or logon screen replacing). The changed winntbbu.dll doesnt appereared at last installation Need i edit that file self that the "server" page of it is modified??? Thanks for any useful answer. A small legal hint: My W2K3 is an evalution copy i use only for development testing purposes...
  19. I just reported XPero that (only differ between your and my complain is lang of error trace)... I work with him together getting rid this error! Chris
  20. I use Avast Home - it doesn't complain anything
  21. XPero: Now, i had already rebooted! Tried again, same. There's only one installation of Vize, the actual 0.5!
  22. I use Vista Ultimate (no sp1) Sorry about the german log, but see in the codebox: Informationen über das Aufrufen von JIT-Debuggen anstelle dieses Dialogfelds finden Sie am Ende dieser Meldung. ************** Ausnahmetext ************** System.UnauthorizedAccessException: Der Zugriff auf den Pfad wurde verweigert. bei System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) bei System.IO.__Error.WinIOError() bei System.IO.File.Move(String sourceFileName, String destFileName) bei Vize.MainApp.patcherWorker_DoWork(Object sender, DoWorkEventArgs e) bei System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e) bei System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument) ************** Geladene Assemblys ************** mscorlib Assembly-Version: 2.0.0.0. Win32-Version: 2.0.50727.312 (rtmLHS.050727-3100). CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll. ---------------------------------------- Vize Assembly-Version: 0.2.0.0. Win32-Version: 0.2.0.0. CodeBase: file:///C:/Program%20Files/XPero/Vize/Vize.exe. ---------------------------------------- System.Windows.Forms Assembly-Version: 2.0.0.0. Win32-Version: 2.0.50727.312 (rtmLHS.050727-3100). CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll. ---------------------------------------- System Assembly-Version: 2.0.0.0. Win32-Version: 2.0.50727.312 (rtmLHS.050727-3100). CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll. ---------------------------------------- System.Drawing Assembly-Version: 2.0.0.0. Win32-Version: 2.0.50727.312 (rtmLHS.050727-3100). CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll. ---------------------------------------- VistaControls Assembly-Version: 1.0.0.0. Win32-Version: 1.0.0.0. CodeBase: file:///C:/Program%20Files/XPero/Vize/VistaControls.DLL. ---------------------------------------- System.Configuration Assembly-Version: 2.0.0.0. Win32-Version: 2.0.50727.312 (rtmLHS.050727-3100). CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll. ---------------------------------------- System.Xml Assembly-Version: 2.0.0.0. Win32-Version: 2.0.50727.312 (rtmLHS.050727-3100). CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll. ---------------------------------------- PatcherHelper Assembly-Version: 1.0.0.0. Win32-Version: 1.0.0.0. CodeBase: file:///C:/Program%20Files/XPero/Vize/PatcherHelper.DLL. ---------------------------------------- mscorlib.resources Assembly-Version: 2.0.0.0. Win32-Version: 2.0.50727.312 (rtmLHS.050727-3100). CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll. ---------------------------------------- System.resources Assembly-Version: 2.0.0.0. Win32-Version: 2.0.50727.312 (rtmLHS.050727-3100). CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.resources/2.0.0.0_de_b77a5c561934e089/System.resources.dll. ---------------------------------------- System.Windows.Forms.resources Assembly-Version: 2.0.0.0. Win32-Version: 2.0.50727.312 (rtmLHS.050727-3100). CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms.resources/2.0.0.0_de_b77a5c561934e089/System.Windows.Forms.resources.dll. ---------------------------------------- ************** JIT-Debuggen ************** Um das JIT-Debuggen (Just-In-Time) zu aktivieren, muss in der Konfigurationsdatei der Anwendung oder des Computers (machine.config) der jitDebugging-Wert im Abschnitt system.windows.forms festgelegt werden. Die Anwendung muss mit aktiviertem Debuggen kompiliert werden. Zum Beispiel: <configuration> <system.windows.forms jitDebugging="true" /> </configuration> Wenn das JIT-Debuggen aktiviert ist, werden alle nicht behandelten Ausnahmen an den JIT-Debugger gesendet, der auf dem Computer registriert ist, und nicht in diesem Dialogfeld behandelt. Hint: I use(d) Vize 0.5 and this happens at start of patching before any file is changed! EDIT: My Windows is not a vLited one... no special options. Should i disable system file protection?
  23. Actually Windows 2000 has a native enviroment installation in logical partition- that is what i prefer because it is running very well See also my posting in beneith forum http://www.msfn.org/board/Windows_2000_Pro...at_t105362.html
  24. I've the update version file(s) cause i'm a registered user of a full purchased version. The first look into script seems it doesnt fit my needs yet So, meanwhile i loaded the Vists Ultimate in memory, should i use it of course, hmm ?
×
×
  • Create New...