Specialty Forums
Security and Virus
General Hardware
CPUs/Overclocking
Networking
Digital Photo/Video
Office Software
PC Gaming
Console Gaming
Programming
Database
Web Development
Digital Home

General Forums
Windows XP
Windows Vista
Windows 95/98
Windows Me
Windows NT
Windows 2000
Win Server 2008
Win Server 2003
Windows 3.1
Linux
PDAs
BeOS
Novell Netware
OpenVMS
Solaris
Disk Op. System
Unix
Mac
OS/2

Drivers
Driver Scan
Driver Forum

Software
Automatic Updates

BIOS Updates

My Computing.Net

Solution Center

Free IT eBook

Howtos

Site Search

Message Find

RSS Feeds

Install Guides

Data Recovery

About

Home
Reply to Message Icon Go to Main Page Icon

Subject: A newcomer to BeOs

Original Message
Name: lapointe34
Date: April 3, 2006 at 15:02:50 Pacific
Subject: A newcomer to BeOs
OS: Windows XP SP2 Home
CPU/Ram: p4 2.8
Model/Manufacturer: Me/myself/and I
Comment:
Hello, I've two questions concerning BeOs for I'm considering to give it a try...
1- this best describes my system: pentium 4 2.8 ghz dual channel with 1gb on an asus p4p800-vm, will personal run, or will I have to get the next version up?
2- Like linux, it partions over partion, this time if I don't want Beos, will I be able to delete the chunk of partion of my main partion with fdisk or any utility>
thanks again


It's higly illogical to state a computer made the mistake for it was us human beings who programmed it.


Report Offensive Message For Removal

Response Number 1
Name: jefro
Date: April 3, 2006 at 15:30:13 Pacific
Subject: A newcomer to BeOs
Reply: (edit)
There are a few ways. BeOS is an OS but has some versions that are really mostly the same but have minor changes. Those changes affect how one can run it. There are even live CD's that you don't need to have installed. As with all live cd's they run slower as they run from the CD (cd's are much slower than hard drives)


A few things.
One is that the original personal edition was a neat way to try beos. It used a virtual hard drive that was just a file that contained the demo OS. It also had a limit of the ram that a system could have. It needed dos and an older version of NTFS. If you have a fat partition then you can use PE with a special boot floppy that limits ram. We are only talking about the original PE on fat partition.

2- A partition on an x86 box is for most people and OS's the same exact thing. The format of the partition changes how the OS uses that partition. You can partition it just like any other OS. YOu can use Windows ot make or destroy or change the partition. You can not use windows to format it for beos yet. I would not install the BeOS boot manager. It does at least offer a way to save the original MBR unlike all linux distro's I have seen.

Your only problems might be ntfs and the amount of ram. Ram can be fixed and ntfs can't be just yet -again PE version only.

Consider using a live demo that yellowtab has of their Zeta OS. It is a BeOS version with some minor changes. You can't install it.

See bebits dot com for all the beos choices and boot floppies to limit ram. See also bezip dot de for more apps. See betips dot net too for problems.



Report Offensive Follow Up For Removal

Response Number 2
Name: lapointe34
Date: May 2, 2006 at 05:50:52 Pacific
Subject: A newcomer to BeOs
Reply: (edit)
Ya, the live CD's are a pain, just like the Suse Linux disks.

It's higly illogical to state a computer made the mistake for it was us human beings who programmed it.


Report Offensive Follow Up For Removal



Use following form to reply to current message:

   Name: From My Computing.Net Settings
 E-Mail: From My Computing.Net Settings

Subject: A newcomer to BeOs

Comments:

 
  Homepage URL (*): 
Homepage Title (*): 
         Image URL: 
 


Data Recovery Software



Version Tracker Pro
Keep your software current and secure, effortlessly

Click Here for a Free Scan

Driver Agent
Automatically find the latest drivers for your computer.
Click Here for a Free Scan



The information on Computing.Net is the opinions of its users. Such opinions may not be accurate and they are to be used at your own risk. Computing.Net cannot verify the validity of the statements made on this site. Computing.Net and Computing.Net, LLC hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy.
PLEASE READ THE FULL DISCLAIMER AND LEGAL TERMS BY CLICKING HERE

All content ©1996-2007 Computing.Net, LLC