I'd say that we should show:
- Run or install ReactOS
- Boot from hard disk
- Advanced options
Nothing more should be needed and the first option should be clear that can either lead to a live environment or a setup.
David Quintana (gigaherz) <gigaherz at gmail.com> wrote on Tue, July 4th, 2017, 10:45 PM:
> I feel like the boot menu is going to be far too busy for the end user. I'd
> go with something closer to
>> blah blah:
>> - Install Now
> - Try without installing
> - Show advanced options...
>> where:
>> - Install now -- boots into the graphical installer (no desktop unless
> you cancel or something)
> - Try without installing -- boots into livecd desktop (backed by RAM, I
> guess)
> - Show advanced options... -- opens a second-level menu with
> - Text-mode installer
> - Live boot without Ramdisk
> - etc.
>>>> On 4 July 2017 at 21:45, Herm猫s B脡LUSCA-MA脧TO <hermes.belusca at sfr.fr> wrote:
>> > Hello everyone,
> >
> >
> >
> > One of the long-term plan for ReactOS was to have a graphical user-mode
> > interface for the 1st-stage setup, similar to e.g. what may be found in
> > newer versions of Windows (Vista+), as an alternative to our current 1st-stage
> > setup in text-mode
> >
> > (note that I say 鈥渁lternative鈥�, not 鈥渞eplacement鈥�, because both of them
> > can live together without fundamental changes to either ReactOS or our ISO
> > images, both of them can share core functionality, and finally because some
> > people may prefer the text-mode either for unattended installations or for
> > low-memory conditions).
> >
> >
> >
> > You can find some information about the 1st-stage GUI setup here:
> > https://reactos.org/wiki/First_Stage_GUI_Setup . In our source code, it
> > can be found in base/setup/reactos/ . Currently only most of the screens
> > have been implemented, while the core functionality is not present. However
> > this functionality can somehow be taken by reusing the source code of
> > USETUP (see my branch https://svn.reactos.org/svn/reactos/branches/setup_
> > improvements/base/setup/ ).
> >
> >
> >
> >
> >
> > Abstract (aka. TL;DR): I explain below the needed changes introduced
> > experimentally in the 鈥渟etup-improvements鈥� branch, revision 75273, to
> > generate an all-in-one ReactOS bootcd, that includes both the 1st-stage
> > text-mode setup + 1st-stage GUI setup alternative + live-demo
> > functionality. This is meant to replace our currently separated 鈥渂ootcd鈥� /
> > 鈥渓ivecd鈥� ISOs, where the latter currently do not offer the possibility to
> > install ReactOS. Some currently known potential problems are evoked.
> >
> >
> >
> > Images: Proposed BootCD contents : http://i.imgur.com/EBA6JHd.png ;
> > Proposed Boot Menu : http://i.imgur.com/14n5Ryi.png .
> >
> >
> >
> >
> >
> > Having a 1st-stage GUI setup also means that it鈥檒l also use the
> > already-existing functionality that we offer in our 鈥淟ive-CD鈥� ISOs.
> > Currently, the 鈥淟ive-CD鈥� ISOs we provide only allow for demonstration
> > purposes, while the ReactOS installation proper is found in our so-called
> > 鈥淏oot-CD鈥� ISOs (which currently only contain text-mode setup). Thus, the 1
> > st-stage GUI setup, as an alternative to the 1st-stage setup in
> > text-mode, means that both ISOs can be merged all in one, and we won鈥檛 have
> > to make a distinction between both: they will be able to offer both the 1
> > st-stage in text mode AND a graphical mode (脿 la 鈥淟ive-CD鈥�) where it is
> > possible to choose whether to test ReactOS in demo mode, or to install it
> > via the GUI setup.
> >
> > Such an all-in-one ISO capability was already present in the trunk under
> > the name 鈥渉ybridcd鈥�, but was used only when we built ISO images for the
> > public events where ReactOS participated (FOSDEM, CLT, 鈥�). But now, having
> > the setup process both in text mode and in graphics mode, in addition to
> > the Live-CD demonstration capability, really suggests just using the
> > all-in-one ISO and stop doing the 鈥淏oot-CD鈥� (aka. only setup) vs. 鈥淟ive-CD鈥�
> > (aka. only demo) separation. We would just generate only one type of ISO
> > that contains everything.
> >
> >
> >
> > With that in mind, I have committed in my branch 鈥渟etup_improvements鈥�, in
> > revision 75273 : https://svn.reactos.org/svn/reactos?view=revision&
> > revision=75273 such changes to be able to only build an ISO that contains
> > everything. These changes are minimal, in the sense that I haven鈥檛
> > purposelessly changed the names of the build targets just to be fancy. Such
> > changes may be done later, but not now.
> >
> >
> >
> > The needed changes are the following: First, the build target that will
> > generate the all-in-one CD is called 鈥渂ootcd鈥�, because this also was the
> > main build target for ISOs before the change. Second, I completely remove
> > the 鈥渉ybridcd鈥� build target, because its functionality are now absorbed by
> > 鈥渂ootcd鈥�. Third, the build target 鈥渓ivecd鈥� is reduced to its strict
> > minimum. For the sake of building a RAMDISK boot drive (see comments
> > after), I continue to generate an ISO for 鈥渓ivecd鈥�. But I鈥檝e changed the
> > generated name to 鈥渓iveimage.iso鈥�, to emphasize the point that it has to be
> > understood as a (virtual) disk image for RAMDISK purposes, not just as a
> > ISO image. Note that I haven鈥檛 renamed the build target 鈥渓ivecd鈥� to, say,
> > 鈥渓iveimage鈥� to reduce my commit changes (such a renaming may be done
> > later). The 鈥渓ivecd鈥� target builds a list of files that need to be present
> > in the image. The generated liveimage.iso is no-more a bootable ISO, I鈥檝e
> > removed inclusion of freeloader + El-Torito boot-sector + the
> > USB-ISO-Hybrid functionality for it.
> >
> > The 鈥渂ootcd鈥� target has been slightly changed in order to include the
> > liveimage.iso as a file (for RAMDISK), and to also add the contents of this
> > image in a flattened tree within the bootcd iso: the two directories
> > 鈥淧rofiles鈥� and 鈥渞eactos鈥�.
> >
> > The 1st-stage text-mode setup is kept, as said before, but its
> > corresponding files + the installation CAB source + the 1st-stage GUI
> > setup application proper goes into a (renamed) directory called 鈥渋386鈥�,
> > corresponding to installation files for an i386 installation (technically,
> > 1 per architecture when we鈥檒l have a ReactOS ported to other archs). These
> > files cannot be present in the same 鈥渞eactos鈥� directory as the ones from
> > the flattened LiveImage, because some of the files are different (smss.exe,
> > registry, etc鈥�) Our FreeLdr knows from where to boot the 1st-stage
> > text-mode (from i386), as well as the Live-demo in graphics mode (from
> > reactos).
> >
> > I need to adjust the code of few setup components for them to stop relying
> > on hardcoded 鈥渞eactos/鈥� path, and instead use a more 鈥渄ynamic鈥� (determined
> > at runtime) path.
> >
> >
> >
> > NOTE FOR DEVS/SYSADMINS: The 鈥渂ootcdregtest鈥� build target, generating the
> > special ISO that is fed to our test bots, remains exactly the same, and the
> > files contained in the generated ISO have not changed.
> >
> >
> >
> > NOTE about the RAMDISK feature: I enabled it so that a user can remove the
> > demo media (CD, 鈥�) and reuse the drive for other purposes, while still
> > being able to use ReactOS. Of course this requires a large amount of RAM
> > available. And that鈥檚 also why I include the flattened liveimage files so
> > that one can use the demo without the RAMDISK (when few memory is
> > available).
> >
> > As is currently implemented, this makes the ReactOS all-in-one bootcd
> > large (it gains a good 100 MB) due to duplicated space (the flattened
> > files, plus the same inside 鈥渓iveimage.iso鈥�). I cannot do better (unless
> > ditching either the RAMDISK, or keeping it but not include the flattened
> > files) because ReactOS currently doesn鈥檛 have a way to boot from disk
> > images **that are not meant to be a RAMDISK**. The day when this
> > difficulty is removed, a single disk image could be used either as the
> > RAMDISK or the (non-removable) installation.
> >
> > A second remark is that I don鈥檛 plan to have the 1st-stage GUI setup
> > available when booting ReactOS in RAMDISK mode because, as a consequence of
> > its current implementation, I would otherwise need to duplicate the
> > installation CAB source in the RAMDISK image too, making it again larger.
> >
> >
> >
> > NOTE about the FreeLdr Boot Menu: Since ReactOS is not that stable
> > currently, we like to boot it in debug mode, and redirect the output to a
> > serial port (usually COM1). However some people don鈥檛 have serial ports on
> > real hardware, so we propose to boot with debug output redirected to
> > screen. However this may slow ReactOS down, so we also like to boot ReactOS
> > with debug mode disabled. That鈥檚 why I proposed the declination of these
> > boot modes for each ReactOS installation contained in the BootCD
> > (Live+Setup, with or without RAMDISK, and with debug enabled or not). The
> > problem is that it clutters a lot the boot menu. A remedy would be to
> > implement in FreeLdr the functionality of editing **existing** boot
> > entries to change their associated boot options, so that one could add by
> > hand the options to enable (or disable) debugging. This is currently
> > unimplemented. The only implemented feature is to set up a new boot entry
> > on the fly to boot ReactOS afterwards.
> >
> >
> >
> > NOTE for regress-testers: Possible remark that I may hear: 鈥淚 only care
> > about installing ReactOS (perhaps just in unattended mode) and I don鈥檛 care
> > at all about the GUI setup nor about the Live-demo thingie, and your new
> > BootCD is too large. I want to be able to download & use the good-old
> > bootcd for regress-testing.鈥� . So what to do? Since we currently build and
> > store the 鈥渂ootcdregtest鈥� ISOs, but are not publicly available through our
> > www.reactos.org/getbuilds interface, I would suggest here to make them
> > available to people, so that those who want to quickly DL and/or
> > install/regress-test ReactOS could use these ISOs instead (which are really
> > just the good old BootCDs, but with unattended installation enabled **and**
> > with our test-suite included). They are not that much large, just a bit
> > more than the old regular bootcd.
> >
> >
> >
> > Please let me know whether you have other remarks/comments/questions/suggestions/etc鈥�
> > to make the new BootCDs better.
> >
> >
> >
> >
> >
> > Best,
> >
> >
> >
> > Herm猫s
> >
> > _______________________________________________
> > Ros-dev mailing list
> > Ros-dev at reactos.org
> > http://www.reactos.org/mailman/listinfo/ros-dev
> >
More information about the Ros-dev
mailing list
CHAPTER VII. THE FOUR CLASSES OF SOCIETY. THE FOUR CLASSES OF SOCIETY. "After the herald had given the names of the wrestlers who were to make the first round, the fellows came in. They were dressed without any clothes to speak of, or rather they were quite undressed, with the exception of a cloth around their loins. They came in on opposite sides of the ring, and stood there about five feet apart, each man resting his hands on his knees, and glaring at the other like a wild beast. They[Pg 231] looked more like a pair of tigers than human beings, and for a moment I thought it was not at all unlike what a bull-fight in Spain might be. I turned upon her choking with anger, but her melting beauty rendered me helpless. Black woods were on our left. "Shall we turn in here?" I asked. "None of that with me," he growled. "Do you know who I am, Countess Lalage? I am Leon Lagage, Count of the Holy Roman Empire, and your husband. Incomparable woman, you cannot alter that fact. For better or worse, for richer or poorer, till death do us part!" I have in this way imperfectly indicated a methodical plan of generating a design, as far as words alone will serve, beginning with certain premises based upon a particular work to be performed, and then proceeding to consider in consecutive order the general character of the machine, mode of operation, movements and adjustments, general arrangement, strains, special arrangement, and proportions. ‘Alas! what is life, what is death, what are we, 11th January two best dresses. Commencement was as usual, with a few showers “All right,” agreed Sandy. “Dick, you and I are the ground crew. As soon as you’re ready, Mr. Whiteside, we’ll take hold!” Effects of Walpole's Administration—Formation of the new Ministry—Attitude of the Malcontents—Committee of Inquiry into Walpole's Administration—Walpole's Protectors—Ministerial Measures—Prorogation of Parliament—Disasters of the French—British Division in the Netherlands—Opening of Parliament—The German Mercenaries—Amendment of the Gin Act—George goes to Germany—Stair and De Noailles in Franconia—Stair in a Trap—Bold Resolution of King George—The Battle of Dettingen—Resignation of Stair—Retreat of the French—Negotiations for Peace—Treaty of Worms—Pelham becomes Prime Minister—The Attacks of Pitt on Carteret—Attempted Invasion of England—Its Failure—Progress of the French Arms—Frederick II. invades Bohemia—His Retirement—Resignation of Carteret—Pelham strengthens his Ministry—Death of the Emperor—Campaign in Flanders—Battle of Fontenoy—Campaign of Frederick II.—The Young Pretender's Preparations—Loss of the Elizabeth—Landing in the Hebrides—The Highland Clans join him—The First Brush—Raising of the Standard—Cope's Mistake—He turns aside at Dalwhinnie—Charles makes a Dash for Edinburgh—The March to Stirling—Right of the Dragoons—The "Canter of Coltbridge"—Edinburgh surprised by the Highlanders—Charles marching against Cope—Battle of Prestonpans—Delay in marching South—Discontent of the Highland Chiefs—The Start—Preparations in England—Apathy of the Aristocracy—Arrival of the Duke of Cumberland—Charles crosses the Border—Capture of Carlisle—The March to Derby—Resolution to retreat—"Black Friday"—The Retreat—Recapture of Carlisle—Siege of Stirling—Battle of Falkirk—Retreat to the Highlands—Cumberland's Pursuit—Gradual Collapse of the Highlanders—Battle of Culloden—Termination of the Rebellion—Cruelty of the Duke of Cumberland—Adventures of the Young Pretender—Trials and Executions—Ministerial Crisis. The next morning he was up betimes, and cooked the boys as good a breakfast as he could out of the remainder of his store and what he could get from the hospital, and then gave what was left to whoever came. The comfortable crib, which had cost the Deacon so much labor, had been pre-empted by the Surgeon for some of his weakest patients. "You two step forward one pace," he commanded. "Gentleman, I've got my six. The rest are yours." "Where are you goin'?" he said sternly. Every now and then the crowd would break into the latest rhymings of MacKinnon's poet: A large thicket, at this moment, gave the dusty foot an opportunity of doubling, and, for an instant, diverging from the straightforward course, though it availed him little, he seemed to feel the breath of his pursuer on the back of his neck; his foot sounded as if at his heels; he drew his garment closely around him, turned suddenly to the right, and, bounding from the ground, the next instant a splash was heard in the little river, and the fugitive was safe from his pursuer. HoME明日之后怎么免费刷一级纳米材料
ENTER NUMBET 0018www.qydp.net.cn www.rctq.com.cn www.jugatebuy.com.cn laijianshen.com.cn xbndjkwlw.com.cn dblj795.com.cn www.wvedu.com.cn xuf888.com.cn www.toyl.com.cn pxsteel.com.cn