Jump to content











Photo
- - - - -

ReactOS

grub2 iso boot

  • Please log in to reply
37 replies to this topic

#26 911CD.net

911CD.net

    Member

  • Advanced user
  • 55 posts
  •  
    United States

Posted 23 February 2018 - 09:59 PM

:lol:  Well, that certainly wasn't the approach I was considering.  I thought I would have to resurrect my old BartPE system and look into rebuilding the ReactOS ISO.

 

I copied the ReactOS ISO to the root of the drive, renamed it livecd.iso, and changed the initrd16 to /livecd.iso  but I got the same results as before.

 

Maybe an initrd16 rdpath=$iso will work. :huh:  Or, maybe an old chainloader +1 command.   :D



#27 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 14379 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 25 February 2018 - 11:10 AM

It is more likely that you have to extract the FREELDR and FREELDR.INI (and maybe some other bootloader file, haven't checked if REACTOS has something like NTDETECT.COM) to root of the device and chainload it (without using memdisk at all).

 

 

:duff:

Wonko



#28 911CD.net

911CD.net

    Member

  • Advanced user
  • 55 posts
  •  
    United States

Posted 26 February 2018 - 01:48 AM

Well, there is no FREELDR that I can see.  And the autorun.inf doesn't help.

Microsoft Windows [Version 10.0.16299.248]
(c) 2017 Microsoft Corporation. All rights reserved.

C:\Users\Ed>dir g:\
Volume in drive G is ReactOS
Volume Serial Number is 2DDC-30E8

Directory of g:\

11/24/2017  03:45 PM    <DIR>          Profiles
11/24/2017  03:31 PM                43 autorun.inf
11/24/2017  03:45 PM    <DIR>          efi
11/24/2017  03:31 PM             1,120 freeldr.ini
11/24/2017  03:31 PM            50,534 icon.ico
11/24/2017  03:45 PM    <DIR>          loader
11/24/2017  03:45 PM    <DIR>          reactos
11/24/2017  03:31 PM             2,692 readme.txt
               4 File(s)         54,389 bytes
               4 Dir(s)               0 bytes free

C:\Users\Ed>type g:\autorun.inf
[autorun]
open=readme.txt
icon=icon.ico

C:\Users\Ed>dir g:\loader
Volume in drive G is ReactOS
Volume Serial Number is 2DDC-30E8

Directory of g:\loader

11/24/2017  03:45 PM    <DIR>          .
11/24/2017  03:45 PM    <DIR>          ..
11/24/2017  03:45 PM         1,474,560 efisys.bin
11/24/2017  03:41 PM             2,048 isoboot.bin
11/24/2017  03:42 PM           346,112 setupldr.sys
               3 File(s)      1,822,720 bytes
               2 Dir(s)               0 bytes free

C:\Users\Ed>

$%#@ I should not have to boot to another system and use a different browser to insert code/text into this forum.

 

Ok, Edge works.

 

The loader folder shows an isoboot.bin and a setupldr.sys.  What do ya think?

 

I'm going to try:

 

initrd16 /loader/sysupldr.sys



#29 911CD.net

911CD.net

    Member

  • Advanced user
  • 55 posts
  •  
    United States

Posted 26 February 2018 - 03:21 AM

initrd16 /loader/sysupldr.sys

 

Resulted in /loader/sysupldr.sys not found message.

 

initrd16 (loop)/loader/sysupldr.sys

 

Resulted in colored pixels on the screen, about 5 columns worth, then hung.

 

I believe I see the colored pixels on the screen, but in only a single column, when I've booted and end up at the list of drivers screen.

 

Does this give you any ideas?

 

# https://reactos.org/wiki/User:Petr-akhlamov/RAM_from_HD
#        set root=(hd0,msdos3)
#        chainloader +1
#        parttool (hd0,msdos3) boot+
#        multiboot /loader/setupldr.sys


#30 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 14379 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 26 February 2018 - 10:58 AM

Strangely enough if a file setupldr.sys exists and you try to chainload a file sysupldr.sys INSTEAD something "queer" may happen.

 

Anyway, I feel like there won't be any progress on the matter until you have (a very large part of) your homework done by someone else.   :frusty:

 

Instructions:

1) make a new folder somewhere on your hard disk, DO NOT use stupid paths including spaces

2) expand in the new folder the attached file

3) copy to the new folder\Source\ the ReactOS-0.4.7-Live.iso

4) rename it to livecd.iso

5) run the BuildreactOS.cmd

6) in the folder a new .iso named LiveCDRAM.iso should be created

7) try using the newly created LiveCDRAM.iso in your experiments

 

:duff:
Wonko

Attached Files



#31 911CD.net

911CD.net

    Member

  • Advanced user
  • 55 posts
  •  
    United States

Posted 26 February 2018 - 03:38 PM

:huh: So much for having the ability to copy&paste. :o   I gotta stop posting after drinking wine.  :lol:  I can assure you the command in the grub2 menu had the correct spelling.

 

Beginning to wonder if this ISO is worth the effort.  Good grief.

 

Thanks Wonko.



#32 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 14379 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 26 February 2018 - 04:19 PM

 I gotta stop posting after drinking wine.   :lol: 

As long as the wine was good, it's fine  :drunk: .

 

 

:duff:

Wonko



#33 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 14379 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 02 March 2018 - 10:01 AM

A side-side note.

Since I had this nice "liveCD" made I played a little bit with it.

 

Once again I am unfortunately unimpressed by the last version of ReactOS :( not that the good guys haven't worked (a lot) or that the new release is not much better than earlier ones, but it still is little more than a toy.

 

Problem of the day:

I tried making a small hard disk (image) to test a few booting options.

 

It seems like there is no way (short of using the "text mode" setup) to partition and format a hard disk in ReactOS.

 

There is seemingly no tool for patitioning.

After a little bit of searching I found PartMod:

https://sourceforge....dproject/files/

that works in ReactOS and can actually create partitions just fine.

Though the distor inculdes a "fatfs.dll" it seems like PartMod has no provisions to actually format a volume.

 

So I created the partition and attempted to use "format" (which seemingly is a formatx by Mark Russinovich/Sysinternals dated 1999) and it didn't work.

 

After some more searching, i found out that the nice Ridgecrops' programs (FAT32Formatter and GUIFormatter) worked just fine:

http://www.ridgecrop...m?guiformat.htm

 

But that allowed only FAT32.

 

So I went down the lane of the good ol' XPCLI project and took good ol' COMPUAPPS SWISSKNIFE for a test.

I used the "BartPE" version for obvious reasons.

https://web.archive....nife-BartPE.exe
 

 

And it can both partition and format just fine under ReactOS.

 

Once a volume has been formatted, seemingly the built-in Format/Formatx seems like capable of re-formatting it, I'll have a look if I can find what "switches" the behaviour. :unsure:

 

:duff:

Wonko



#34 dencorso

dencorso

    Frequent Member

  • Advanced user
  • 141 posts
  •  
    Brazil

Posted 05 March 2018 - 10:01 PM

IMO, ReactOS is letting it's best chance of advertising how great it really is slip between its fingers: if they prioritized (which they haven't) their universal USB 3.x xhci driver they began working on last semester, they'd have the opportunity of seeing it adopted by the XP die-hard comunity, which still commands some 5% of the desktop market share, because Intel dropped XP from their USB 3.0 drivers... but if nothing happens soon, by Dec 2019, if not earlier, XP will have reached the 0% market share mark, and by then the launch of such drivers will only interest retro hobbyists and a few other odd users, at most.



#35 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 14379 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 06 March 2018 - 01:58 PM

...but if nothing happens soon, by Dec 2019, if not earlier, ...

 

Countdown to July 9, 2019:

https://www.timeandd...09&font=cursive

 

... already less than 490 days ...

 

:duff:

Wonko



#36 911CD.net

911CD.net

    Member

  • Advanced user
  • 55 posts
  •  
    United States

Posted 06 March 2018 - 03:40 PM

the XP die-hard comunity, which still commands some 5% of the desktop market share,

Really!!   :o   I'm surprised it's that high.

 

But I'm sure that 5% is on old hardware with no USB ports let alone USB 3.x ports so I can understand the reluctance to develop USB 3.x drivers.



#37 dencorso

dencorso

    Frequent Member

  • Advanced user
  • 141 posts
  •  
    Brazil

Posted 06 March 2018 - 06:43 PM

Countdown to July 9, 2019:

https://www.timeandd...09&font=cursive

 

... already less than 490 days ...

 

• Windows Embedded Standard 2009, Extended Support will end on Jan. 8, 2019.
• Windows Embedded POSReady 2009, Extended support will end on April 9, 2019.

 

Are you betting on 0% by July 9, 2019, already?  :dubbio:



#38 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 14379 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 06 March 2018 - 07:34 PM

• Windows Embedded Standard 2009, Extended Support will end on Jan. 8, 2019.
• Windows Embedded POSReady 2009, Extended support will end on April 9, 2019.
 
Are you betting on 0% by July 9, 2019, already?  :dubbio:

Yes and no, July 9 is roughly three months after April 9, 2019, which is IMHO a "reasonable" time for those actually believing in updates to accept the loss and change OS, but I expect that there will be a "hard core" still using XP well after that.
 
If you prefer I believe (you know my continuous issues with the crystal ball, and my resorting to I-Ching lately [1]) that the current 5% is roughly made:
1-2% of believers in PosReady updates
2-3% of clueless people (that don't know about the issue or that don't care) or people that actually *need* XP or however have not the possibility :( (economical or other) to change OS (which implies in - still say - 71.84% of cases an update to the hardware as well) 
0.1-0.2% of reckless daring bastards (yours truly representing 0.0000000000000000000001% ;) ) that every morning will start by checking the sky (to check it has not fallen) and then go ahead computing happily (if it has not fallen).

 

Reference:

Spoiler

 
Now, whether some of these will be able (besides wanting to, actually be able to) connect to the Internet and thus be counted on Statcounter or similar, it is another thing.  :dubbio:
 
:duff:
Wonko 
 
[1] I got 18:
 
THE JUDGEMENT OF KING WEN:
18. REBUILD FROM RUIN
Inertia And Indifference Have Caused The Situation, To Degenerate. It Is Important, To Understand, What The Problem Caused Before You Try, To Solve It. Keep This Point In Mind, Take Decisive Act First Then. If Care Took In - At Regenerating Of The Situation, A Relapse Does Not Happen.
THE COMMENTARY OF THE DUKE OF CHOU:
Line 1: The Situation Can Be Remedied Still Easily, If You Can Find A Sincere Person, To Help You.
Line 2: Errors, Which Result From Weakness, Have Caused The Degeneration.
Line 3: Which You Have Moved A Bit Too Energetically, To Correct The Problem.

and 22:
 
22. BEAUTY AND ADORNMENT
Beauty And Gracefulness Provide Order And Pleasant Diversity, Which Quiets The Spirit And Fills The Heart With Assessment. Beauty Creates Light, Which Can Illuminate Many Small Questions, But It Becomes With Deep, Controversial Ones Do Not Help.
THE COMMENTARY OF THE DUKE OF CHOU:
Line 2: Is Not Diverted By A Beautiful Exterior. Pay Attention To The Contents.
Line 4: You/They May Miss The Comforts, But You Will Find Much More Meaning And Peace.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users