ChrisKuhli

//--- Few updates in the thread: Misspellings corrected!. ---//

Corrected the links, updated first posting! The old URL www.customwin2000.info redirects now directly to the Project sub page that might be converted to an own blog...

//-- Posting for clarity - might be altered from to to time { Updated inital post a bit for corrcting and reflecting the new situation thread! }

The initial post of this thread reminds me of my draft foundable on my projects site (see signature). As i'm a Delphi coder that doesn't harm with long time of coding i would say that W3bbo startet an awful job with the Rebirth. Sure if ever 2ize then it can't ever concurize with the others cause of Legacy. But the ideas are sharing PLEASE don't harm that i write here as not-concerned but this po(in|s)t might be no advertisment. Just a little thought...

This is the boot code printed out via EasyBCD: Windows Boot Manager -------------------- identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795} device partition=C: description Windows Boot Manager locale de-DE inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e} default {466f5a88-0af2-4f76-9038-095b170dc21c} displayorder {466f5a88-0af2-4f76-9038-095b170dc21c} {868bb5a4-5aaf-11dd-b41d-f232bb970754} toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d} timeout 15 Windows Legacy OS Loader ------------------------ identifier {466f5a88-0af2-4f76-9038-095b170dc21c} device partition=C: path \ntldr description Windows 2000 Professional & Windows XP Media Center Edition Windows Boot Loader ------------------- identifier {868bb5a4-5aaf-11dd-b41d-f232bb970754} device partition=H: path \Windows\system32\winload.exe description Microsoft Windows Vista locale de-DE inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7} osdevice partition=H: systemroot \Windows resumeobject {868bb5a5-5aaf-11dd-b41d-f232bb970754} nx OptIn detecthal I reinstalled Windows 2000 and XP MCE... Install Vista refused to load PLEASE help me! Thanks.

My actual Win2K and the WinXP MCE2005 runs very well... I redid the new booting environment but no running Vista yet. It is independent if i try x86 or x64 DVD to boot and install...

"Legacy" is installed on C: It is Win2K and WXPMCE2005 (after reinstall in the both first partitions of my SATA drive) Booted from Vista's DVD the install stops after the bootmenu was shown! Then afaik when the bootmgr loaded it tries to load the winloader.exe which stops with a black screen. Any hints? Edit: I forgot to say that all system reside on a 200 GB SATA disk on VIA onboard SATARAID (MSI board). Earlier days i had no install problems... *Edit* I found out that enabling the RAID functionality in the BIOS helped me out of these circumstances... You may write now as replies here if is a bad idea to have RAID 0 with only one Sata harddisk! I second having raidsupport but the harddisk isn't configured as a raid of course.

Look Damian666! Surprised? Only the graphic on the left is a bit awful. It might be better to use old-fashioned dialog Chris

Hello I'm sorry but my complain was cause what i made is sooo old As i have no time until Friday - we'll have at weekend new files from me Chris

Good Morning! I've decided for the new fresh native Windows 2000 Professional install using without TrueTransparency, like i described above. BTW the System-Properties are very awful in Windows 2000 Deutsch: Please for Windows Aktivie use "Windows Aktivierung" in german resources instead. Owner ist "Benutzer" and Company is "Firma"."Product-ID" is Produktschlüssel (if last too long write "Schlüssel" only. There is no oemlogo installed... What about that bitmaps and its displying?it looks very strange! Regards, Chris

Damian666, you're today exactly two years @ MSFN As you are a very good competitor i wish you make the best of this saturday in the little hours you might on here As i doesn't want to make this topic cluttered i say you now my overall opinion about the work you make (including all projects here): Vistapack: I use it with my Windows 2000 Professional, with relatively simply options: (no Tclock or Tbar, TrueTransparency for the borders, other options as given by standard). It makes NT5 to the perfect Windows : as i say - everlasting Windows 2000! UTender: As i use in my Windows XP Media Center Edition 2005 the standard theme i don't need it. But it tested it a while ago with corrent result for checking purposes, so its a good tool! vUXTender: For another user account i need to install the Aero Theme "Vista_Classic by UkIntel" which makes this tool possible. Fine I wish all readers an writers in this forum and neighbourhood a nice saturday and ciao, Chris

Hello Dude I'm also sad of XPero's decision but - read below... First the sourcecode of XPize/ Vize is based on C# Older (?) XPize derived projects were based on earlier branch of completly different coding language. Now we need people they are (good) able of CSharp if we want to use the actual sources! These decisions do we need to make: - Want we support the older code branch (See sourcecode of the older XPize/ the XIS)? - Should it be a team of several people working with the sources we now have? CRYING around the msfn board: No one here who can go further with XPize/ Vize? I am NOT a developer using their coding language... As i consider to create patchers with other language i COULD do the fancy but... Bye, Chris

At this time there is no support for XP msstyles in Windows 2000 But there are solutions for Windows 2000 used for example by the VistaPack - see here in the forum Customizing Windows.

To other(s) here in the forum: greg pinned me so ithink he does okay. The only what i think he could break the license he made with the builder of his Laptop if he use this MCE (whatever form modified or not) with other if its EULA is especially related to that hardware.

So, can we then use an mp10 addon to create a real MCE2005 to avoid the mediaplayer downstep?

First i suggest you buy a small set of Rewritable disks One thing i meanture: You write you use an Addon to integrate the MCE. So you don't have original MCE files? Hmm if you want do a legal task...

I could just integrate the released Servicepack with its switch... But does that break the MCE functionality? Thus i use on my minor size partition Win2K only and on the SATA disk Vista only the XP should work in Virtualmachines. So, I my XPMCE convert into an install good for VMs! What should i accomplish not to get rid of mediaplayer - Use m10psetup seperatly?

You need appropiate changes to TXTSETUP.SIF, and some files in XPCD\I386 are different... Any other member here already did that? Might not useful here but I would do the backwards way @greg677: Useful info might be look in this thread (this forum) WindowsXP/2003 Ultimate Edition.

Sorry for this little bumping i made some changes here to make the thingy more clear

The logo is a resource in the file sysdm.cpl (see in this forum). The Windows version string is coded in the system itself (e.g. if servicepack install)... Dunno but i think its a bit strange changing that i mean why should users to be fooled? If you do that needs also all Strings refering to the Windows changing? Do you build for enterprise or private? Cause might be license harm...

Please consider to answer as reply of this posting! Licensing of an application is not trivial. Tell me what you prefer: - closed source freeware (might be General Open License as in XPize) - open source freeware (e.g. GPLv2 GPLv3 BSDLicense) BTW i decided to cut off the poll so its easy for all to reply to the thread Results of the poll:

I tried just a patch of an install.wim with SP1 (Servicepack added w vLite, WAIK f VistaSP1/ WS2K8) . No error were displayed What i know only after a testing install into a VirtualPC how that looks and how Vize re-acts with that... Edit.h tells ya this evening Here some hints for anyone who don't know how to get run this tool (actual version): - edit settings.txt for the correct imagex path! - if your Vize doesn't reside in [C:\Program Files\XPero\Vize] copy its entire path content to there (the patcher code uses ONLY that path atm), like this: - open "h:\program files\" in Explorer (example of my Vista installation) - click directory "XPero" - press the keys CTRL+C - go to C: in the Explorer - create the directory "Program Files" if it not already exists - change to there - press the keys CTRL+V - you see the copying process If path of settings.txt points to the program imagex.exe (e.g. in a complete WAIK installation, have not tested yet if copied out goes also) and Vize can be found at default path the actual Patcher from zedox should run... Questions @zedox: - imagex: A msfn member did an image mounter including it, couldn't you make next patcher versions in same manner? - lazyness: If you are gone out of time for going ahead... I could code with Delphi7 (not the latest but fine) - now, should i overtake or want you develop further? Which development environment did you used until yet? Edit.h says: Development of a project goes longer if time is needed for learning to code

I added that file with the .msu from Microsoft cause normally with SP1 it seems not to be included. I tried Vize with German Ultimate, which i use (now) only with the Servicepack (e.g. integrated via vLite). Okay, i tell it briefly: Reloader stops with error if it tries to patch winhlp32.exe! Then suggestion to reboot. *Very* annoying so i ignore the Vize Notifier Message "1 zu patchende Datei(en) gefunden" ("1 file(s) to patch found" in english i think). Should i try the patch myself and the changing of Vize Logs? Better I get a workaround or solution...

Some useful due to testing possibilities for ckWin is my operating system using history (brief): 1993-2002 MS-DOS6(.2) Win3.1 (again in virtual machine) 1994-2000 OS/2 Warp 3 for Windows(w Win above) (again in virtual machine) 1995-2001 Win95 (again in virtual machine) 1996 (to today) Linux (several distributions) 1998-2000 WinNT4 (again in virtual machine) 2000-2002 Win98 (again in virtual machine) 2000 (to today) Win2k Prof 2002 (to today) WinXP Prof (sold) 2006 (to today) WinXP MCE 2007 (to today) WinVista Ultimate Please write if you: - can test in Windows Me - can test in any WinNT3.x - have server license (any windows) and may work to enable compability with it