93 replies to this topic

[Lancelot]

Hi all,

After ~2 months of work (started ~08.10.2009 with saydin77's home made builder which supports x64 sources) now LiveXP have limited support for x64 sources. (hojope etc. could made this only 2 days ago)
Greeeaaat thanks to Saydin77 without him I could never start this journey.
Thanks to jacklaz to point me qemu x64 support without VT (If this did not happen I must have stopped working on this long while ago)
Thanks a lot to boss (Galapo) , The Dream Boss forever
Thanks to pedrole for the great capi changes.
And Thanks a loooooot to JFX, for the increadible support to the LiveXPx64 project.

ps: It is better to remember and give credit to far sight of Smiley (boot-land member) where an old project from Smiley exists that build x64 which I could never achive... Practically LiveXP is the FIRST wb project that can produce pe1x64 which can be reproduced easly.


How to test:
*
Download current LiveXP Recommended with winbuilder (with default settings)
*
If you do not have a XPx64 or 2k3x64 ENU source, download 2k3x64sp2Trial from bi$$y
http://www.google.co...u...mp;oq=&aqi=
extract and use as source

IMPORTANT: For now only enu versions are supported.

*

Extra Scripts of Current topic:
Additional Apps:
http://lancelot.winb...912082353_v2.7z
http://lancelot.winb...12101243_v1.rar
http://lancelot.winb...retoko_Lance.7z

Something to remember:
*Set Resolution --> detection of emulator needs a fix on Pex64 builds (check post 41 42 43)
*ScreenLock --> not working properly on PEx64 builds
*Virtnet --> Something bugy, either virtnet or penetwork => PEx86 (check post 46)
*modelram.exe at targetsys
*Something about XPSP2RES:
on billy's website, there are 2k3sp2 trials, the enu version contains XPSP2RES but others do not contain XPSP2RES !!!
%xpresfile%=XPSP2RES.dll
[Copy-XpRes]
IniRead,"%ProjectInfo%","OS","XpRes","%XpRes%"
If,%XpRes%,NotEqual,0409,Set,%XpResFile%,SPRT%XpRes%.dll
CopyOrExpand,"%source_win%\%XpResFile%","%target_sys%\XPSP2res.dll"
*Something about SP2:
on billy's website, there are 2k3sp2 trials, the enu version contains sp2.cab but others do not. Maybe others are sp0 !!!
*HDTune ---------------> Not working for now
*JoshuaKeyFinder------> Not working for now


edit: topic first created on a hidden forum.
Since it is now well known LiveXP supports x64, I decide to move topic to public which as a result I hope in some future LiveXPx64 discussions, support and awarness increase and may continue even here.
Have fun.

[Galapo]

Thanks a lot to boss (Galapo) , The Dream Boss forever

Thanks for the nice words.

You have done an amazing job getting all this together. nativeEx/LiveXP fun continues!

Regards,
Galapo.

[pscEx]

Great work!
And you are a very good manager, having so many people working successfully in your team!
For me, it has been funny to fullfill your requests to nativeEx!

Hopefully the last Pentium4 issue will be solved, too.

Peter

[Lancelot]

@psc

I have news (good or bad )
Today I learned that saydin77 never worked on ia64 because he could not find a copy on net.
I sent him 2k3ia64sp2trial link



Edit: Old Post 1 - Additional sp info - moved here to keep post 1 shorter

An extra info for service Pack:
As far as i know there is no servicepack1 for x64 But the released XPx64 (or 2k3x64) can be called sp1 and sp0
Here is the story,
10/25/2001 - Windows XP release
10/25/2001 - Windows XP 64-Bit Edition, Version 2002 for Itanium systems
02/xx/2003 - xp servicepack1a 32bit
03/28/2003 - Windows XP 64-Bit Edition, Version 2003 (support to Itanium 2 processor)
04/24/2003 - 2k3 release (including IA64)
08/10/2004 - xp servicepack2 32bit
03/30/2005 - 2k3 servicepack1 32bit 2k3 servicepack 1 IA64

07/xx/2005 - ***Hewlett Packard, the last distributor of Itanium-based workstations, stopped selling Itanium systems marketed as 'workstations' as of July 2005.
At this point Bill decide not to continue "Windows XP 64-Bit Edition" series and stopped the support. However continue to support 2k3IA64 (hey this is a server )
And Billy decide to support AMD64 since winds are more stronger at that vector :>.
ps: I know 07 is bigger than 04, but lets say HP annouce it will stop selling at 01/xx/2005

04/xx/2005 - 2k3 x64 release
04/25/2005 - Windows XP Pro x64 Edition Release (shortly supporting AMD64 processors (AMD64, IA32, IA-32e and EM64T...))
Info from wikipedia "WinXPx64Pro uses version 5.2.3790.1830 of core operating system binaries, the same version used by Windows Server 2003 SP1"
The trouble is, with releasing "2k3 & XP AMD x64", Billy's Gang decide to continue with the codes of 2k3SP1x86 and named the release with sp1 (WS03SP1 , w2k3sp1). As a result the "released" Windows'es can be called either 2k3sp0x64 - XPsp0x64 or 2k3sp1x64 - XPsp1x64. Keep in mind there is NO sp1.cab or WIN51AP.SP1 or WIN51AA.SP1. They are technically sp0 (released) versions.
03/12/2007 - 2k3 servicepack2 32bit - 2k3 servicepack2 IA64
03/13/2007 - xp/2k3 servicepack2 AMD64
05/06/2008 - xp servicepack3 32bit

It seems, in order not to mix minds,
Billy troopers decide to give 2k3x64 & WinXpPro-x64 "First" servicepack name "ServicePack2" since there is a sp1 for IA64 and x86 with an older date.
However, The initial release of 2k3x64 & WinXpPro-x64 do not contain a sp1.cab (or WIN51AA.SP1 or WIN51IP.SP1) in order to mix minds a bit

Shortly: As far as LiveXPx64 concerned, there is no servicepack1
and I believe LiveXP do not no need to support initial release of XPpro-x64.

ps: for the above info, please correct me if I get mistaken.

Edit: Old Post 1 - Infos not required anymore

(As a result of the progress after the current topic creation date, Strike Outed lines are not required anymore for PE1x64 builds )
*
download capi v15rev4b from here
http://lancelot.winb..._Common_Api.rar
*
click source-->Rules-->"Enable Rules"-->unselect the checkbox===>Click Save Settings

*
Basic\Build\DefineBootsector-->select "Set bootsect.bin as bootsector (normal)"
*
unselect following scripts :
Basic\Build\FIPS
Basic\Build\OleSupport
Components\Core\1 System\addCMDutils
Components\Core\1 System\MMC
Components\Core\1 System\Scripting Core
Components\Core\1 System\Scripting Support
Components\Core\1 System\Network\PENetwork
Components\Tweaks\Set Resolution
Components\Tweaks\WallPaper
--------------
Apps\ (unselect all)
To give example that some Apps works enable
Apps\CDVD\ImgBurn
Apps\File Tasks\a43
Apps\File Tasks\FAR_Manager
Apps\HD Tasks\MBR\MbrFix
--------------
Drivers\2 Video\VMWare Video
Drivers\3 Network\qEmu 0.9.0 Network Driver
Drivers\3 Network\VirtualBox / VMWare Network Driver
Drivers\4 Storage\Build DPs Mass Storage Drivers script
Drivers\4 Storage\LSI plus Bus Logic - SCSI driver for Vmware
Drivers\4 Storage\Removable Devices Combo

Drivers\6 Other\HWPnP
Finish\1 Optimization\Post Processing Tools
Finish\1 Optimization\BootScreen

Update note: Following packages are OLD dated, please download LiveXP through winbuilder for tests,
Since this topic created for our advanced & frequent users of LiveXP, I hope you all succeed
Here is the successfull build log with the above instruction
http://lancelot.winb...1207_002939.rar

And to ease above instruction here is a packed file following the instruction (and i deleted unselected scripts of apps to make package smaller)
http://lancelot.winb...70057_LiveXP.7z
Reminding, this is NOT a special package, all already available at LiveXP server, and scripts continues to update so above list will change in time.

Edit: Here is a never copy including some additions of current topic http://lancelot.winb...eXP_20091212.7z

Extra Scripts of Current topic:
Progress:
http://lancelot.winb...00912182257.rar (going to monkey :>)
http://lancelot.winbuilder.net/5F/PENetwor...2182229_v37g.7z

[was_JFX]

Great work Lancelot

A small thing, I guess Build Model putting default Program files location to registry, they not yet compatible with x64.

This will be needed:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion]

"ProgramFilesDir"="X:\\Program Files"

"CommonFilesDir"="X:\\Program Files\\Common Files"

"ProgramFilesDir (x86)"="X:\\Program Files (x86)"

"CommonFilesDir (x86)"="X:\\Program Files (x86)\\Common Files"

"ProgramFilesPath"=hex(2):25,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,\

  00,69,00,6c,00,65,00,73,00,25,00,00,00



[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion]

"ProgramFilesDir"="X:\\Program Files (x86)"

"CommonFilesDir"="X:\\Program Files (x86)\\Common Files"

"ProgramFilesDir (x86)"="X:\\Program Files (x86)"

"CommonFilesDir (x86)"="X:\\Program Files (x86)\\Common Files""ProgramFilesPath"=hex(2):25,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,\  00,69,00,6c,00,65,00,73,00,25,00,00,00

[Lancelot]

Thanks a lot JFX, I see the missing ones.

@Peter,

I modified buildmodel v84 slightly and put at LiveXP server "(v84b) at description",
I guess we can more easly syncronise with v85 without me making further modifications.

Here is a list of things required from buildmodel v84:
* check buildmodel v84b on livexp server, there is modelram fix there
* JFX request
* Better to have modelram.exe at targetsys than systemroot %systemroot% (%target_win%) instead of %systemdrive%, reasons are:
1) we can have PE1x64 and PEx86 on single cd, but modelram.exe systemroot ....
2) having cdroot more tidy (less files) is better
3) It is easier to have pe1x added to ufd (or other media).


Here are values from my hostos
http://lancelot.winb...136_HKLM_CV.PNG
http://lancelot.winb...6432Node_CV.png

[was_JFX]

MMC working nicely with PE1x64, requires same files like Win2003 x86 and also register msxml3.dll.

Seems it's a bit grumpy against REG_EXPAND_SZ and %Variables%

[Galapo]

A small thing, I guess Build Model putting default Program files location to registry, they not yet compatible with x64.

Do you think it should instead be up to '5 - WOW64_Core.Script' to set these values? '9 - ProgramFilesPE.Script' probably requires some modification, too.

Regards,
Galapo.

[pscEx]

I guess we can more easly syncronise with v85 without me making further modifications.

This morning I downloaded and tested.
Good news: In 'Standard' nativeEx_barebone it runs well.
Bad news: I have troubles with the testVirtualBox.script. Changing the folder of modelram.exe to the new location and testing brought malfunction.
I'm sure that this is an issue of the script itself, not an issue of the new place.
But since this morning I'm hunting the bug and did not catch him yet.

Please give me one more day to accept the change. (I'm sure the change is OK)

Peter

[was_JFX]

Do you think it should instead be up to '5 - WOW64_Core.Script' to set these values? '9 - ProgramFilesPE.Script' probably requires some modification, too.

Could also be done, but I don't think it's good to have to much scripts doing the same thing.
Most important is the creation of these folders (even if empty). Would suggest '9 - ProgramFilesPE.Script' should handle registry and folder creation for simplify.

[pscEx]

Could also be done, but I don't think it's good to have to much scripts doing the same thing.
Most important is the creation of these folders (even if empty). Would suggest '9 - ProgramFilesPE.Script' should handle registry and folder creation for simplify.

@JFX:
You appearently want to fix a bug / issue in the current construction.
But I do not understand completelly what is intended here.

If it is LiveXP internal, "Do what you want"
If it affects the underlying nativeEx functionality, "Please explain for me"

Peter

[was_JFX]

Peter,

this is related to an old request I made to LiveXP project for looong time, the creation of all Shellfolders.
Takes month until it was finally more or less accepted

'Program files' are very important members of Shellfolders, currently this folders are not created in LiveXP x64.
This can take serious trouble to the hole PE.
Please don't ask for reproduce able scenario, but trust me this is a very important thing.

BTW PROJECTINFO.INI have a problem in x64PE

[Cabs]
SP_CAB=driver32.cab

shoud be

[Cabs]
SP_CAB=SP2.cab

[Lancelot]

BTW PROJECTINFO.INI have a problem in x64PE

Hi JFX, for a temporary solution check post 16

btw, today I am in a busy traffic (mostly because of emulator things and the project we work with blue_life), please forgive if i respond a bit late time to time.

[pscEx]

Peter,

this is related to an old request I made to LiveXP project for looong time, the creation of all Shellfolders.
Takes month until it was finally more or less accepted

'Program files' are very important members of Shellfolders, currently this folders are not created in LiveXP x64.
This can take serious trouble to the hole PE.
Please don't ask for reproduce able scenario, but trust me this is a very important thing.

BTW PROJECTINFO.INI have a problem in x64PE

shoud be

OOPS!
That touches fundamental functionality!
In x86 logic, in (source CD) driverindex.inf there is descibed something like:
CabFiles=SP3,driver
That means:

• Service pack #
  
• Where to find latest drivers

In XP x64, we have:
CabFiles=driver, driver32
That means:

• Service pack 'driver' > nonsence
  
• Where to find latest drivers > nonsence(?)

I'll try to resolve this gordian knot!

Peter

[Lancelot]

For me qemu thingy finished nicely (case closed).
Besides I learn a new emulator with qemu taste, bochs. bochs also can boot PE1x64 without trouble on pentium4 .

Well, to have an alternative at hand (and to ease tests), I decide to write a script for bochs emulator, script is unfinished for enduser but I believe very useful for goodusers. I will try to finish this script later when I find time.
Edit: newer version on next post
disadvantages:
*I feel it is slower than qemu (not tested with chronometer )
*I could not have mouse double click work. (I tried some (not all) configurations with mouse settings but failed)
*using a configuration file is questionable (either disadvantage or advantage)

advantages:
*better organised
-->easier to find latest version
-->have installer
-->nice features with graphical interface
-->Easy access configuration menu with a lot of details around.

Currently I have no plan to put bochs script to the project, qemu is fast, small, nice (totally satisfactory). Lets wait what future will show.
I hope you like bochs

[Lancelot]

some more news:

There is no itanium pc around (for us), and there is no itanium emulator for windows, so IA64 support should wait for more time
Keep in mind ia64 as much as possible as an investment for future. It is obvious that last point for PE1 about source support is IA64. I do not know the details, boot management seems changed a lot with probably other things. (no ntoskrnl.exe (where to put /minint ) but there is still ntkrnlmp.exe ) Besides folder structure of the rest at source looks like x64
Maybe there is PE support for IA64 maybe there is not......

ps: I forgot to activate a checkbox with bochs (verry small thingy), here is a fixed version
http://lancelot.winb...912082353_v2.7z
reminding: when custom or hddcustom selected, they are created once and never deleted again. For further changes with custom use "Configure" button.
on the other hand, hddimg and default are recreated at each run, etc etc..

[Lancelot]

2 scripts updated to make further mmc (& other) tests easier (1 no version change)
Also,here is a temporaryfix script to be used with ENUx64 source.
http://lancelot.winb...00912092113.rar

@JFX,
what is next to make mmc work

[was_JFX]

@Lancelot
Thanks a lot for Fix Shell folders

For MMC only type

regsvr32 /s msxml3.dll

in command prompt after boot, than it should work fine.

We could capture registry settings, but mmc (x64 only ??) seems to need hard coded paths, but you guys love these %Systemroot% ...

So may putting the line into Autorun keys or Galapo compiling us an x64 version of ExpEnvVar.exe , we could use here

Edit: Upps MMC.script missing

If,%SourceArch%,EQUAL,X64,require_file,credui.dll in Section [InstallServices]

[Galapo]

Galapo compiling us an x64 version of ExpEnvVar.exe , we could use here

Should already be available for use.

Regards,
Galapo.

[Lancelot]

Thanks a lot JFX
mmc script updated
also here is a new fixshell
http://lancelot.winb...00912101039.rar

and here is regshot2unicode script (just made)
http://lancelot.winb...12101243_v1.rar

seems to need hard coded paths, but you guys love these %Systemroot% ...

The Reason behind this Love is the Blue Eyes that makes boot envolve less things
For mmc case some examples (any time, not urgent) to show why hard coded paths needed on registry will be very helpful.

Well, now only diskmanagement do not work

[was_JFX]

Thanks a lot for nice regshot script

For mmc case some examples (any time, not urgent) to show why hard coded paths needed on registry will be very helpful.

Okay %variable% not problem here, more a buggy of bad mmc.scirpt.

The in script attachet reg files overwrite the default value of a key from msxml3.dll to msxml.dll.
So if you want to add registry capture of regsvr32 /s msxml3.dll, it have to be done on the very end of script.

Well, now only diskmanagement do not work

Hmm, tricky one, well 'll take a look at this.



EDIT: MMC script (and CoreMain script) overwrite my correct line

RegWrite,HKLM,0x7,"WB-Setup\ControlSet001\Control\Session Manager\Memory Management",PagingFiles,""

with their wrong one

RegWrite,HKLM,0x7,"Tmp_setupreg_hiv\ControlSet001\Control\Session Manager\Memory Management",PagingFiles,"NUL: 0 0"

[Lancelot]

Thanks a lot JFX

no more unwanted page file anymore (both MMC script and CoreMain script updated)
+ msxml3.txt added to mmc for pe1x64 builds

[was_JFX]

Here's working MMC script.

Disk managment now also working for Windows Sever 2003 x86

BTW: This fix show a general bug of LiveXP with Server 2003

[Lancelot]

Thanks a lot JFX,

I did not notice this BUG before

New MMC script on server, also added *temporary hardcoded shortcut creation for startmenu. MMC was a huuuggggeee step which I will not succeed without your help. With this step I guess now things will go a bit faster

[was_JFX]

So with MMC done, choose the next one