You can use any operating system of your choice, providing that this is linux with kernel 2.4 or 2.6. We are building, developing and testing on Debian and kernel 2.6 is recommended. If you have any compilation issues on any other linux distributions, please, report them to the mailing list.

The general idea is that you copy the first sector of your native root FreeBSD partition into a file in the DOS/NT partition. Assuming you name that file something like c:\bootsect.bsd (inspired by c:\bootsect.dos), you can then edit the c:\boot.ini file to come up with something like this: [boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows NT" C:\BOOTSECT.

It may, but do not have to. You may put your kernel image at a fixed MTD partition at the beginning of the flash chip and feed the rest of the flash to UBI. The point is that you do not have to give UBI whole flash chip, you just give it some MTD partition.

Enter sysinstall(8) and choose Configure, then Fdisk. Select the disk the Boot Manager resided on with the space key. Press W to write changes to the drive. A prompt will appear asking which boot loader to install. Select this, and it will be restored.

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.

Answer: There are settings in Interact development and on the PowerStation that need to be adjusted. In Interact under the FILE menu select Interact Settings and then select your Startup Application on the General Tab. Then in the Application Browser, Under Application Manager, Select Application Settings. Then on the General Tab under Startup Mode choose Run and make sure that you have chosen the appropriate Startup module.

This is classically a case of FreeBSD and DOS or some other OS conflicting over their ideas of disk geometry. You will have to reinstall FreeBSD, but obeying the instructions given above will almost always get you going.

Add something like this to your /etc/lilo.conf file under linux and rerun /sbin/lilo. Note that Solaris *MUST* be the active partition, on either the primary or another another hard drive. To use LILO with Solaris on the primary partition, install LILO in the MBR and mark the solaris partition as active. In this example Solaris is on your second hard drive (hence the "loader" line): other = /dev/hdb1 loader = /boot/chain.

FreeBSD's boot loader is incorrectly recognizing the hard drive's geometry. This must be manually set within fdisk when creating or modifying FreeBSD's slice. The correct drive geometry values can be found within the machine's BIOS. Look for the number of cylinders, heads and sectors for the particular drive. A dialog will pop up requesting the number of cylinders, heads and sectors. Type the numbers found from the BIOS separates by forward slashes.

The general idea is that you copy the first sector of your native root FreeBSD partition into a file in the DOS/Windows NT partition. Assuming you name that file something like c:\bootsect.bsd (inspired by c:\bootsect.dos), you can then edit the c:\boot.ini file to come up with something like this: [boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows NT" C:\BOOTSECT.

Make sure you upgrade to the newest version of E-Loader to ensure the most trouble free performance. The previous version of E-Loader had issues with the version of Java it used, this has been remedied in the current release which can be download from the E-Mu website.

The general idea is that you copy the first sector of your native root Solaris/x86 partition into a file in the DOS/NT partition. Assuming you name that file something like c:\bootsect.sun (inspired by c:\bootsect.dos) you can then edit the c:\boot.ini file (copy boot.ini to boot.

Facilities that are applying for a Title V permit will be given a new PI number that will replace the existing NJID number. This change facilitates the implementation of the Department’s new computer system. You should obtain the new PI number before applying for an operating permit. You can easily obtain a PI number by calling the operating permits hotline at 609-633-8248.

Deployed applications will run on any operating system and hardware supported by your target Java EE application server. Today, Mainsoft's integration with the Visual Studio IDE level is supported for IBM WebSphere Application Server 6.0, 6.1; IBM WebSphere Portal 5.1 and 6.0; and Tomcat 5.5 (as a Web-container). Mainsoft will provide development support for additional application servers in the future.