Remember, the IO is basically a standard pentium class PC with a standard BIOS and a 16MB flash memory card. Please read some of the messages in the "Technical" area on the I-Appliance Discussion Forum BBS, you will find many posts there talking about different OS's and how other installations went.

Not likely. Given that only very few musicians use BeOS or Linux as their main OS for making music, it's just not worth the effort. BeOS is definitely programmers heaven with its clean, OO APIs, love em, but anyone actually uses BeOS? If bZone gets ported to another OS, it'll be MacOS.

The basic platform of Atlantis is Win32 (Windows 95/98/NT/ME/2000/XP/Vista). No other platforms are yet supported.

Then you can resize the hard drive, shrinking the XP partition and then create a new partition from the available free space. Then you will be able to install Linux on the new partition. for the tools available to resize the partition, you could check if there is still a trial of Partition Magic. How about. When people get something solved, they post back to there original post to say so. Just to let other people know that are having the same problem that this may be the way to solve it.

DISCLAIMER: Messing around with boot loader issues can make your harddisks unbootable. Please make backups before doing so. Please install a new boot loader only when you really now what you do. We reject any responsibility for damages that may occur on your system. GRUB - the GRand Unified Bootloader - needs to access some files in order to run. Its best you place them on a small - 50MB is enough even for further extensions - FAT 16/32 partition.

You can configure your computer to start Windows 2000, Windows NT, and either Windows 95 or Windows 98. However, you cannot configure a computer to multiple boot Windows 95 and Windows 98. Both Windows 95 and Windows 98 use the same boot file. Therefore, multiple booting Windows 95 and Windows 98 at the same time is not supported. Your installations are less prone to problems if you install Windows 95 or Windows 98 before you install Windows NT and Windows 2000.

It's amazing how many folks have a favorite platform. Many of us here do also. We're thinking about all of these seriously-- in some cases we may even have prototype drivers up in the lab. But nothing to announce... yet.

Currently, we support the Vortex 2 completely on the Windows 9x operating systems, and basic audio functions under Windows NT 4.0. We are working with other developers to develop drivers for alternative operating systems. In the cause of Linux, 4Front Technologies is working on supporting Vortex 2 in their OpenSound package.

Booting into Linux is easy, all you need is a recent copy of Penguin (the booter) and a kernel. (Both of which can be found on this site under "Downloads".) Before you can boot into Linux, you will need to turn off Virtual Memory and you may need Mode32 (see the section on Mode32, later). Start up Penguin, select the kernel that you want to boot from in the configuration screen, and then use the boot option from the file menu. If it works, you'll get a message about rarp requests.

If you're running Pro, you can use GPEDIT.MSC to prevent Messenger from loading. Otherwise, even disabling it in startup won't cause it to "always" not run. Outlook, Outlook Express and some Microsoft web pages can still make it load. You can now modify whether it starts initially and/or whether it is to run at all. If you don't have Pro, run Windows Messenger, Tools, Options and uncheck "Run this program when Windows starts".

Go to Explorer, insert a floppy disk, right-click on the A Drive, click Format, check Make System disk and click OK.

Sure, you can. Create a primary partiton BEFORE your Windows partition (e.g. with PartitionMagic) and get a boot manager (I use the german tool 'Bootmanager', you can get a free trial version at http://www.bootmanager-pro.de).

No. The lmhostid is used to calculate the key, not the server hostname. The lmhostid should be the same for both since it comes from the Ethernet card. Since it is the same, the user should have two copies of his license file. The one for Windows should have the server name set to the Windows server hostname. The Linux license file should have the server hostname associated with the machine when booted under Linux.

No. Stickies is a Windows program. If I had a Mac, maybe I'd look into coding my version of Stickies for it, but even if I did, it's taken me long enough to learn how to write for Win32, let alone working out an entirely new windowing coding API. Like it or not, Windows is the most prevalent desktop OS in the world. Of course, if you own a Mac, then you'll know that there's already a similar application on your machine, also called Stickies.

Short answer is -- noway. This is protected mode, use OS services instead. Again, you can't use int 0x10, int 0x13, etc. Fortunately almost everything can be implemented by means of system calls or library functions. In the worst case you may go through direct port access, or make a kernel patch to implement needed functionality, or use LRMI library to access BIOS functions.

Sooner or later, most people who own an S-100 system need to transfer a file to or from a DOS or Windows (or Macintosh or whatever) computer. A Google search of comp.os.cpm "groups" will find a discussion of this very topic that last occurred in early 2003. It's an old topic. Most people who need to establish serial file transfers to or from a CP/M system (or N* DOS system) of ANY sort end up doing something like this: get a SIMPLE file transfer program onto their CP/M system.

It makes no difference what operating system you are running on your PC; Windows and Mac should work just fine. All you need is Internet access, a web browser that will let you get out on the Internet and access your site, and an FTP program that you can use to connect to your site.

You can very easily run Linux and Windows on the same computer, switching between them whenever you want. There are a couple of different ways to do it, most distributions use a program called LILO (LInuxLOader) that gives you a prompt when your computer boots that you type either 'linux' or 'windows' into depending on what you want to do.

The most common reason for this problem is the absence of a bootable master boot record or active partition on the target disk. When using the Copy a specific drive method to copy one drive to another, Casper Tech Edition does not replace the master boot record or change the active partition status on the target disk. In order to ensure the target disk contains a valid master boot record and the appropriate partition is marked active, it is necessary to use the Copy an entire hard disk method.

R-Studio works on Windows 95/98/ME/NT/2000/XP/2003 only. It will not work under DOS or another operative system which fits into one bootable floppy. Therefore, you should attach your hard drives to another computer which can boot to Windows, and then restore files on that computer using R-Studio. No matter how that system recognizes your drives, R-Studio should access it.

Yes, both grub and lilo can boot Windows from an NTFS Volume. What actually happens, is that the Linux boot loader finds the NTFS boot loader and gives control to it.

You looked at the status web page and your machine was supported. But it just won't boot! Why not? Well, there are a few common problems that cause most of these failures. The most common one is that you're trying to use an ancient kernel that doesn't properly support your hardware. You should always be using the latest kernel, unless you have a really good reason not to. Other common problems are less obvious.

No. (Older dmsdos versions supported it, but this feature has been given up when the CVF-FAT interface was introduced. Well, the documentation always warned ... ) What can I say. You decided to use compressed partitions - now you are experiencing one of their greatest disadvantages. But dmsdos has some special tricks for you in this case. You can..

Either by typing the kernel arguments at the BOOT lilo: prompt, or by adding an ''append='' directive to the /etc/lilo.conf file; for example: At the LILO prompt (example only): BOOT lilo: parport=0x3bc,7 parport=0x3bc,none serial=0x3f8,4 serial=0x2f8,3 If you modify the /etc/lilo.conf file, be sure to run the lilo command to install the new configuration.

The floppy might have bad sectors on it, use a different floppy (one w/o bad sectors). See previous for creating a Linux boot-disk under DOS. See Q. 52 for creating bootdisks. Yes! This card is supported under Linux but the drivers are not currently part of RHL 6.2. You can get the source from here: http://www.scyld.com/network/ethercard.html

If LILO doesn't work, and if the machine has MS-DOS or Microsoft Windows, you may be left with a computer that won't boot. This can also happen on an upgrade to your Linux distribution. Re-installing LILO is the last thing that the installation does. So it is vitally important when installing or upgrading Linux on a dual boot machine, to have a MS-DOS or Windows rescue disk nearby so you can FDISK -MBR. Then you can go about using LOADLIN.EXE instead of LILO.

If you have FreeBSD and Linux on the same disk, just follow LILO's installation instructions for booting a non-Linux operating system. Very briefly, these are: Boot Linux, and add the following lines to /etc/lilo.conf: other=/dev/hda2 table=/dev/hda label=FreeBSD the above assumes that your FreeBSD slice is known to Linux as /dev/hda2; tailor to suit your setup). Then, run lilo as root and you should be done. If FreeBSD resides on another disk, you need to add loader=/boot/chain.

If LILO doesn't work, and if the machine has MS-DOS or Microsoft Windows, you may be left with a computer that won't boot. This can also happen on an upgrade to your Linux distribution. Re-installing LILO is the last thing that the installation does. It is vitally important when installing or upgrading Linux on a dual boot machine, to have a MS-DOS or Windows rescue disk nearby so you can FDISK -MBR. Then you can go about using LOADLIN.EXE instead of LILO.

No, no, and no. SkyOS is an operating system written from scratch. It isn't based on any other operating system. No. This is the Crystal icon pack created by the very talented Everaldo, used in SkyOS with his blessing. This icon set is also used by KDE for Linux, which is why the icon sets look similar. SkyOS uses its own GUI system called "SkyGI", which features a complete C++ API. This system has nothing to do with X or XFree86, and is not based on either of these systems or their forks.