It is not normal but weird that a propietary OS code supposely gets leaked and the copyright holders shut up. It is weird that an updated version like Dano gets leaked and the copyright holders shut up. It is not normal that BeOSPE gets hacked to be installed beyond its pretended limits and the copyright holders and authorized distributors shut up.
It is also weird that somebody releases a BeOS 5. All of these is not normal life. As long as Palm owns BeOS copyright and trademarks, insisting on using them is not a good idea. OBOS is a great name by itself that, unlike Be or BEOS or OpenBeOS, as far as I know some rigorous precautions should be taken concerning a documented study of possible prior similar trademarks can succesfully pass the no trademark infringement test.
Forget Palm, and lets try to go beyond BeOS after cloning it. COM , not be. This is a typical matter to be addressed within Beunited. Is this ISO file really bootable? Will it boot if no OS is installed on the dedicated box, no partition created? So is this really a stand alone version? You can burn the mb beos. If you do not have a bootmanager i. Or have not tried have BeOS. Follow me on Twitter EugeniaLoli. Is this the way BeOS is destined to go? If you want to see a mess, that was Vb in the uni labs i work in today not working because of day light saving… yes thats right setting the clock back an hour killed VB… As for ReOS, as far as i can tell, its just a distribution method for OpenBeOS and other software.
What a mess! Other Linux based one? Its BeOS 5 with some updates. What he said!!!! I had forgotten about the google translator, great service! Good to see that the BeOS fans are alive an kicking. I really hate PE for depending that much on a host operating system…. But not of BeOS. We have loads already. Nor is BlueOS. Please, tell me what is BlueOS a fork of other than Linux!? Worth checking out if you like to explore niche operating systems.
Between the two, VMware Workstation was the clear winner for speed of installation, responsiveness, and once configured could comfortably run at 1, x 1, display resolution.
On the other hand, VirtualBox just needed some extra time for loading on startup and would work up to 1, x 1, resolution. Both only support up to bit colour. I gave it a shot with the following options selected, essentially the same as what I would set up for Windows Once done, select OK to close the dialog box.
The next few steps is really about sorting out the hard disk. Initially when the Installer window is shown, select Setup partitions after expanding More options.
Select Setup from the menu and choose intel from the Partition sub-menu. A dialog box will appear to cover over file systems and partitioning of the hard disk.
Select OK to confirm the configuration. A warning message will pop up that changing partitions will cause data to be destroyed. Select Proceed. Returning back to Drive Setup the hard disk would have expanded in the list of devices now reflecting its partitions. A dialog box will appear to select the file system block size and the name of the volume. I left the block size at the default of 1, , though elsewhere read to use 2, instead.
Either option should be fine; select Initialize. When asked whether to mount the partition, select Mount. After the previous steps have been done, Drive Setup should know have details displayed in the File System and Volume Name columns. Now you can close Drive Setup, either by selecting the top left square of the window, or via the Mount menu.
Select Begin and installation of BeOS commences. The Installer should now state that installation was successful. Unmount the floppy disk image and select Quit to reboot the VM. If all goes well BeOS should successfully load to the desktop albeit with a warning message about the display.
Those familiar with setting up Windows, will find the process of installing drivers and such a bit unconventional. The first thing to sort out is the display to not only see things in colour but as a side effect the mouse will perform substantially better.
Search for vesa and return the search results. A small file named the same should appear. Repeat the previous steps and search for drivers as a separate window. For the vesa file, double-click on the path location. In the drivers search window, double-click on the folder itself located at the aforementioned path. The way BeOS operates is that clicking on the file or folder directly will open it, but clicking on the path will open where the file or folder is located instead.
Opening up both destinations you should have windows display showing the contents of both the sample and drivers folder. Returning the search results.
To be honest, R5 isn't as big an improvement over R4. This isn't to say that there aren't great new features, but rather that there are some key ones that were left out more on that later. While a more comprehensive list of the improvements found in R5 is here , I've decided just to cover a few of the points that I feel are most important. You really should check out Be's site just to see all the full list of improvements and random hardware that is now supported like mouse wheels, yay!
Starting with the R5 betas, I experienced some audio crackling issues common to the users of some soundcards. Thankfully these appeared to just be an issue with the betas, because my sound quality is back to its wonderful self with R5 both Pro and PE.
One thing that really irritated a number of users is that OpenGL support was removed from R5. Be's reasoning is that they were in the middle of re-writing it, and didn't want to either a release something that was very incomplete, or b waste time updating the old OpenGL drivers to R5. At any rate, the OpenGL beta is closed to the general public. Be does have the necessary documentation for ATi's chipsets, but they are hoping that someone will step forward and offer to write the drivers for them.
Nvidia, on the other hand Don't attempt to read anything into the previous sentence. You'll just make yourself frustrated. It would be nice if Be would open up the OpenGL beta to the general public and let people decide whether or not they want to risk their systems with unsupported and very experimental code.
However, Be prefers to release nice, polished tidbits once in a while for the public's consumption, so you'll have to wait until they decide that the OpenGL rewrite is ready. The first two are self-explanatory and straightforward. The latter brings up a helpful window to help you manage the application links and folders that are shown in the Be menu. While you can still do that and for some people it's easier , many users will elect to use this new feature.
Click to see a larger image. Bundled FS support All the newly-included filesystem support drivers were available separately from third parties previously, but it's nice to have them included now by default.
0コメント