X64 Options

[jeradr]

Will UBCD4WIN work with 64-bit Windows (Core2Duo procs)? I can't seem to get it to work on any of the new Dell systems coming through.

[hilander999]

What hal is being used on the new Dell's?



I know some 64bit processors will work with bartpe, but it will require a few tweaks & you might need to get the hal file off of one of the new systems that does not work with the project.

[jeradr]

What hal is being used on the new Dell's?



I know some 64bit processors will work with bartpe, but it will require a few tweaks & you might need to get the hal file off of one of the new systems that does not work with the project.

How would I determine that? That will be upsetting if it doesn't work with new 64-bit Dells :\ That's all we're getting in as of late, no more 32-bit processors.

[SteelTrepid]

It could also just be that minor "bug" in PreShell?? Some of the processes PreShell runs and terminates happens too quickly on these new faster processors. Joshua has made a few tweaks to it and I think this user would be a good candidate for beta testing the new version?

[jeradr]

It could also just be that minor "bug" in PreShell?? Some of the processes PreShell runs and terminates happens too quickly on these new faster processors. Joshua has made a few tweaks to it and I think this user would be a good candidate for beta testing the new version?

On a side note, should you build a boot CD using X64 files? I've pointed the builder to the location of the folder which contains the I386 folder for an x64 Windows CD. However if you click on the plugins button for example, you get the error: "Please enter a valid source path first (file "c:\winxpx64\i386\ntdll.dll" not found)."

[hilander999]

It could also just be that minor "bug" in PreShell?? Some of the processes PreShell runs and terminates happens too quickly on these new faster processors. Joshua has made a few tweaks to it and I think this user would be a good candidate for beta testing the new version?

On a side note, should you build a boot CD using X64 files? I've pointed the builder to the location of the folder which contains the I386 folder for an x64 Windows CD. However if you click on the plugins button for example, you get the error: "Please enter a valid source path first (file "c:\winxpx64\i386\ntdll.dll" not found)."

X64 SOURCES will not work.



Describe (IN DETAIL) exactly what error you are recieving and exactly when it is being displayed.

[jeradr]

It could also just be that minor "bug" in PreShell?? Some of the processes PreShell runs and terminates happens too quickly on these new faster processors. Joshua has made a few tweaks to it and I think this user would be a good candidate for beta testing the new version?

On a side note, should you build a boot CD using X64 files? I've pointed the builder to the location of the folder which contains the I386 folder for an x64 Windows CD. However if you click on the plugins button for example, you get the error: "Please enter a valid source path first (file "c:\winxpx64\i386\ntdll.dll" not found)."

X64 SOURCES will not work.



Describe (IN DETAIL) exactly what error you are recieving and exactly when it is being displayed.

I'll post it as soon as I set up another X64 machine. Should be sometime today, I appreciate the help.

[rdsok]

The hardware is not what is in question... its the version of Windows that can not be the 64bit version .. the processors can be without affecting anything.

[jeradr]

The hardware is not what is in question... its the version of Windows that can not be the 64bit version .. the processors can be without affecting anything.

It was an unrelated question. The boot disk was made with an XP 32-bit sp2 CD. Tomorrow i'll be setting up another X64 machine so I'll see if it works (it hasn't in any previous attempts).

[steje]

Also, what model servers are you working with - I'm booting ok on Dell PowerEdge 1950 and GX620 systems...

[jeradr]

Also, what model servers are you working with - I'm booting ok on Dell PowerEdge 1950 and GX620 systems...

This is a Dell Precision 390 I'm working with, UBCD4WIN 3.0, 1.9 Driver Pack. I get to the boot screen, select "Launch boot disk", it goes through the detecting system configuration stage, I get the XP Loading screen, the blue background comes up (this is where it should prompt you with the shell stuff) and it just hangs. It never loads virtual Windows environment. This same boot disk will work on any 32-bit machine in the office.

*update*

Strange I've let it sit here for about 10 minutes (the CD-ROM lite is solid, although I don't hear any activity), and the mouse cursor finally came up. Still nothing further though as far as it loading.

*update 2*

Just received this error: drwtsn32.exe -Bad Image
X:\i386\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.0.0_x-ww_1382d70a\comctl32.dll is not a valid Windows image. Please check this against your installation diskette.

*update 3*

After clicking OK on the above error I got this blue screen error:

STOP: c000021a {Fatal System Error}
The windows Logon Process system process terminated unexpectedly with the status of 0xc0000354 (0x00000000 0x00000000).
The system has been shut down.

*update 4*

Ok i'm dumbfounded, I rebooted and it boots in to the virtual environment now but it can't load drivers for the network card (even though it's a Broadcom). Now for the fun of trying to add drivers to the build for the first time. Would this be any different on an X64 machine? I'm assuming so.

This post has been edited by jeradr: Dec 7 2006, 05:30 PM