Recent Posts

Pages: 1 ... 8 9 [10]
91
Boot Managers / Re: Plop Boot Manager on ReactOS
« Last post by Gerald on July 24, 2018, 00:47:46 AM »
Quote from: Elmar on July 21, 2018, 14:46:00 PM
I created a dirty fix to start the Plop Boot Manager from the FreeLdr Boot Menu. I will add it to the download section when its tested by someone else.

I had some troubles with installing ReactOS in virtual machines (qemu and Virtualbox). At first, I would say, ReactOS should remove the install option from the Live CD. The error message "Userinit failed to start the installer!" is not helpful. It would be better to tell the user, that this CD can't be used for installing ReactOS. And the second problem was, after installing ReactOS from the correct CD, I got a blue screen. The debug log told me "hive header failed". Hmmm. After installing a few times, finally the problem was that the virtual hard disk was too small. I can't remember, that I have seen an error message about that during the install process. Booting worked fine with a hard disk of 5 GB. Later, I saw the disk had about 2 GB of data stored. Previous, my virtual hard disk was only 500 MB big. I don't want to register to the ReactOS forum because of those few problems, and maybe those are my faults. Now its here documented. Ok, ReactOS boots.


The patch: https://download.plop.at/files/bootmngr/plpbt4win-freeldr-patch.zip

Patch instructions:

1) Run the batch script "01-freeldr-patch1.bat". This creates the file "c:\boot.ini".

2) Run "InstallToBootMenu.bat" from the Plop Boot Manager "Windows" directory.

3) Run the batch script "02-freeldr-patch2.bat". This creates the file "c:\plop\plpfreeldr.ldr".

4) Open "c:\freeldr.ini" with an editor.

5) Add in the "[Operating Systems]" section the line
PlopBootManager="Plop Boot Manager"

6) Add at the end of the file the lines
[PlopBootManager]
BootType=BootSector
BootDrive=0
BootPartition=1
BootSectorFile=\plop\plpfreeldr.ldr

7) Save the freeldr.ini file.

8) Optional, if you want, you can remove the dummy file "c:\boot.ini".

Then reboot.

Note: Native loading of the new boot manager from FreeLdr is still on the todo list.

Best regards
Elmar

Well it works. Plop Boot Manager starts normally, 'HDA Partition 1' is loaded when selecting in Plop menu.. but it does not detect an inserted CD-ROM (in this case an .iso mounted in QEMU environment).
92
Boot Managers / Re: Plop Boot Manager on ReactOS
« Last post by Elmar on July 21, 2018, 14:46:00 PM »
I created a dirty fix to start the Plop Boot Manager from the FreeLdr Boot Menu. I will add it to the download section when its tested by someone else.

I had some troubles with installing ReactOS in virtual machines (qemu and Virtualbox). At first, I would say, ReactOS should remove the install option from the Live CD. The error message "Userinit failed to start the installer!" is not helpful. It would be better to tell the user, that this CD can't be used for installing ReactOS. And the second problem was, after installing ReactOS from the correct CD, I got a blue screen. The debug log told me "hive header failed". Hmmm. After installing a few times, finally the problem was that the virtual hard disk was too small. I can't remember, that I have seen an error message about that during the install process. Booting worked fine with a hard disk of 5 GB. Later, I saw the disk had about 2 GB of data stored. Previous, my virtual hard disk was only 500 MB big. I don't want to register to the ReactOS forum because of those few problems, and maybe those are my faults. Now its here documented. Ok, ReactOS boots.


The patch: https://download.plop.at/files/bootmngr/plpbt4win-freeldr-patch.zip

Patch instructions:

1) Run the batch script "01-freeldr-patch1.bat". This creates the file "c:\boot.ini".

2) Run "InstallToBootMenu.bat" from the Plop Boot Manager "Windows" directory.

3) Run the batch script "02-freeldr-patch2.bat". This creates the file "c:\plop\plpfreeldr.ldr".

4) Open "c:\freeldr.ini" with an editor.

5) Add in the "[Operating Systems]" section the line
PlopBootManager="Plop Boot Manager"

6) Add at the end of the file the lines
[PlopBootManager]
BootType=BootSector
BootDrive=0
BootPartition=1
BootSectorFile=\plop\plpfreeldr.ldr

7) Save the freeldr.ini file.

8) Optional, if you want, you can remove the dummy file "c:\boot.ini".

Then reboot.

Note: Native loading of the new boot manager from FreeLdr is still on the todo list.

Best regards
Elmar
93
Boot Managers / Re: Plop Boot Manager on ReactOS
« Last post by Gerald on July 21, 2018, 00:05:57 AM »
Quote from: Elmar on July 17, 2018, 10:11:12 AM
Hello,
I will spend some time to support native loading of the new boot manager from the Windows boot menu. The new boot manager has a completely different kernel as the Plop Boot Manager and makes it easier to add that feature. Native loading from FreeLoader (FreeLdr) should work too. But first, other things have priority.

Take your time...
When ReactOS bootloader is supported by Plop, let us know please.
94
Boot Managers / Re: Plop Boot Manager on ReactOS
« Last post by Gerald on July 21, 2018, 00:02:41 AM »
Quote from: Gerald on July 17, 2018, 00:04:39 AM
Copying \freeldr.ini to \boot.ini and running the batch again.
Then copying the boot.init over the freeldr.ini.

I tested doing this: Plop install well but, ReactOS doesn`t boot into Plop menu.

95
Boot Managers / Re: Plop Boot Manager on ReactOS
« Last post by Elmar on July 17, 2018, 10:11:12 AM »
Hello,

Quote from: Gerald on July 17, 2018, 00:04:39 AM
Could 'plpbt.bin' be used if specified its path in 'FreeLdr.ini'?

No. plpbt.bin is a 16 bit program that is bigger than 512 bytes and cannot (as far as I know) started directly from freeldr.ini. Thats the reason why there is the workaround with plpbt4win.exe on Windows systems. It creates a kickstarter to load plpbt.bin from the Windows boot menu.


Quote from: Gerald on July 17, 2018, 00:04:39 AM
Could plop add support to be installed on ReactOS?

I will spend some time to support native loading of the new boot manager from the Windows boot menu. The new boot manager has a completely different kernel as the Plop Boot Manager and makes it easier to add that feature. Native loading from FreeLoader (FreeLdr) should work too. But first, other things have priority.

Best regards
Elmar
96
Various, HFS+ Rescue, Sitemap generator, other tools / Re: Source code of plop bootmanager
« Last post by Gerald on July 17, 2018, 00:13:40 AM »
Quote
my boot manager is 100% assembler, if you don't understand the basics how the usb hardware works, then you don't understand the source code. for me its no surprise that my boot manager is currently the only one that supports usb boot from uhci, ohci and ehci.

best regards
elmar

Will you release Plop source code (as GPL 2 +, BSD, MIT) one day Elmar?
Do you seriously consider  to do?
97
Boot Managers / Plop Boot Manager on ReactOS
« Last post by Gerald on July 17, 2018, 00:04:39 AM »
Trying to install Plop Boot Manager on ReactOS (a Windows XP-like OSS OS) fails with "unsupported operating system" error.

It has  a different bootloader than Windows XP:

'FreeLdr' instead of 'Ntldr' and for boot entries has 'FreeLdr.ini' instead of 'Boot.ini' .

Could plop add support to be installed on ReactOS?
Or is there a trick to install plop successfully on ReactOS?

Not doing this:
Copying \freeldr.ini to \boot.ini and running the batch again.
Then copying the boot.init over the freeldr.ini.
(The idea is to install plop on ReactOS without its bootloader modification).

Could 'plpbt.bin' be used if specified its path in 'FreeLdr.ini'?

More info about:
https://jira.reactos.org/browse/CORE-14827
98
Plop Linux / Re: Copy2Ram broken on 4.3.5
« Last post by The_Raven on June 27, 2018, 16:07:25 PM »
3.2GB i know. But it sees only <2GB. :o

Option 1: Find out why it see's only 2GB
Option 2: Find out why rootfs need 1.6GB
99
Plop Linux / Re: Copy2Ram broken on 4.3.5
« Last post by Elmar on June 27, 2018, 16:04:49 PM »
The i486 version should see about 3 GB RAM.
100
Plop Linux / Re: Copy2Ram broken on 4.3.5
« Last post by The_Raven on June 27, 2018, 15:59:43 PM »
Wait, something is strange :o
I use the i486 version of plop.
And it see's "only" 1942196kb of RAM.
Why?
If it has only <2GB, and the rootfs is 1.6GB -> no wonder that it does not work!
But i ask me why is the rootfs 1.6GB when booting from USB and only 932MB from PXE? :o
Maybe because of the customized initrd?
Pages: 1 ... 8 9 [10]