92 replies to this topic

[Waulk]

Either download manually or from the download centre from the following server: livexp.boot-land.net.

Regards,
Galapo.

Ahh, THERE it is! Thanks!

For poor benighted souls like me, how would I find this or similar information in the future? Is there some button or location where I can go to find each of the projects?

[Galapo]

For poor benighted souls like me, how would I find this or similar information in the future? Is there some button or location where I can go to find each of the projects?

It's there by default in the download centre unless manually removed. Same for other projects.

Regards,
Galapo.

[Waulk]

It's there by default in the download centre unless manually removed. Same for other projects.

Regards,
Galapo.

Sorry to be so incredibly dense, but where is the "download centre", and how does one navigate to it in general?

When I click on the "Downloads" button in the top bar it takes me somewhere, but definitely not to the download centre you are talking about.

When I click on the Wiki button in the top bar I am informed "Boot Land wiki has a problem" -- this happens *every* time I try it. So I don't try it very often any more.

I tried searching for the phrase "download centre" and didn't see anything that looked promising.

I am amazed at the incredible information available at BootLand, as well as the wonderful technical expertise that is freely given here. The tutorials are wonderful, the forums informative, and overall it is a hugely positive experience. That's why it's such a shock when I run into these disconnects, such as I am told where to find things by name (download centre) but cannot find anything that tells me where it actually is!

It doesn't help that many of the internal links within BootLand point to pages that have moved, so they resolve to the Forums home page. That also makes it difficult to find related information that I know is somewhere, but not where the links point to anymore.

Sorry to vent my frustration, but I have spent hours just trying to *find* the stuff when I wanted to spend those hours trying to *understand* the incredible riches that are here.

Again, the quality of the material, the helpfulness of the participants, and the general tenor of the site are outstanding. But there are a few gaps that noobs like me fall into and have great difficulty traversing.

Thanks!

[Galapo]

The download button takes you to the Download Center. By default you'll get the following:



Notice that the LiveXP server is included and selected by default.

Regards,
Galapo.

[Waulk]

Clearly we're talking about different buttons -- and I'm still looking for the one you are using.

When I click on the Downloads button I am taken to this screen:


Where's the button you're talking about?

Thanks!

[Galapo]

It's on the WinBuilder interface:



Regards,
Galapo.

[Waulk]

Thanks Galapo!

That probably explains why I could not find it anywhere on the BootLand fora.

[matte]

I still got 0x0000007b error.. Done the tutorial ( http://www.boot-land...?showtopic=4111 ). Anyone got a clue?

This is the error, 0x0000007B (0xF79D6528, 0xC0000034, 0X00000000, 0x00000000) .

[matte]

I tried the 'Recovery build' and the 'Delux build', both just keeps booting in Qemu.

Edit: Solved, uninstalled VirtualBox and then it worked.

[matte]

I still got 0x0000007b error.. Done the tutorial ( http://www.boot-land...?showtopic=4111 ). Anyone got a clue?

This is the error, 0x0000007B (0xF79D6528, 0xC0000034, 0X00000000, 0x00000000) .

Anyone?

[Galapo]

Possibilities: you need 2k3 ramdisk.sys. Maybe you need to include your storage controller.

Regards,
Galapo.

[matte]

Possibilities: you need 2k3 ramdisk.sys. Maybe you need to include your storage controller.

Regards,
Galapo.

Tried with 2k3 ramdisk.sys, says corrupted file when booting.

[Galapo]

Tried with 2k3 ramdisk.sys, says corrupted file when booting.

I've never had that message myself. Seems you're doing something wrong. You'll need to post a log so Amalux or myself can see what you're trying to do with your build.

Regards,
Galapo.

[matte]

I've never had that message myself. Seems you're doing something wrong. You'll need to post a log so Amalux or myself can see what you're trying to do with your build.

Regards,
Galapo.

Im using recovery build ( http://www.boot-land...?showtopic=4111 ) and XPSP2. It works fine when booting in QEMU and with CD.

[Galapo]

Like I said, please post a log so we can see what's happening. Without it, we're only guessing.

Regards,
Galapo.

[matte]

Galapo you got PM.

I thing is strange..it boots up from the USB memory, it shows the booting LiveXP with the | | | | | | (and so one). but when its done loading that the microsoft windows screen (see below) shows, (and loading) THEN the blue screen comes.

[Galapo]

Well, yes, of course. That's typical of a ramdisk.sys error.

Regards,
Galapo.

[Galapo]

If you want Amalux's input as the developer of the project, you'll need to post the log here rather than PM it to me only.

Based on your log, it would seem to be either: a) incorrect ramdisk.sys version (confirm version); or b) need to make use of the modified ntdetect.com.

Regards,
Galapo.

[matte]

Incorrect ramdisk.sys you say, SP2 instead of SP3 or how do you mean?

[Galapo]

I mean: it needs to be w2k version. I forget if 2k3 sp2 version is OK, but preferably add sp1 or r2 as with matching setupldr.bin.

Regards,
Galapo.

[matte]

Tried with a w2k version of ramdisk.sys and setupldr.bin, no luck. Still windows loading screen..

When i tried with a 2k3 version, it said corrupted..ist there any more files than ramdisk.sys and setupldr.bin i have to copy from my cd to the usb and replace?

[matte]

Jisses im tired of this now.
I have tried both 2k, 2k3 and xp. 2 computers. Same thing..

[was_jaclaz]

To recap, this info has been written almost everywhere, but you never know:
Windows 2000 files will NOT work
Windows XP files will NOT work
Windows Server 2003 files will NOT work
Windows Server 2003 SP1 files WILL work
Windows Server 2003 SP2 files may (or may NOT) work
Windows Server 2003 R2 files WILL work

The files STRICTLY needed are:
SETUPLDR.BIN
RAMDISK.SY_/RAMDISK.SYS

Optionally:
NTDETECT.COM

jaclaz

[Galapo]

From the log I know that he has the correct setupldr.bin file. Unknown is ramdisk.sys, and that's the information I've tried to gain. No clear answer on that one yet.

Regards,
Galapo.

[matte]

To recap, this info has been written almost everywhere, but you never know:
Windows 2000 files will NOT work
Windows XP files will NOT work
Windows Server 2003 files will NOT work
Windows Server 2003 SP1 files WILL work
Windows Server 2003 SP2 files may (or may NOT) work
Windows Server 2003 R2 files WILL work

The files STRICTLY needed are:
SETUPLDR.BIN
RAMDISK.SY_/RAMDISK.SYS

Optionally:
NTDETECT.COM

jaclaz

Thanks, must have missed that.
Can i use XP to do the iso and then copy the files from 2k3?