Sponsored Content
Full Discussion: Error F painit on bootup
Operating Systems SCO Error F painit on bootup Post 303015039 by jgt on Monday 26th of March 2018 08:31:28 PM
Old 03-26-2018
What is the manufacturing date of the replacement board?
Boards manufactured since mid 2012 (designed for Windows 8) can cause issues.

You may be able to determine if the mb is usable by:
Boot the motherboard from an SCO 5.0.7 cd, (with or without a hard disk), and see how far you can get with the installation.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Triple bootup

Hi guys, May I know how to install Solaris 8 in the way that I can triple boot it with my the other two OS: WIndows ME and Windows 2000 Pro. Can you all please kindly advise me on how to setup the triple boot process inorder to allow Windows ME to be the default OS when being ask to choose... (1 Reply)
Discussion started by: cia
1 Replies

2. Linux

Preventing a scan of the RAID during bootup

I have a RH 7.3 server that needs a restart today after putting a patch in place. The last time I rebooted this box was almost a year ago and when the uptime is quite long, Linux likes to check all the disks for errors, including the RAID. This adds almost 1.5Hrs to my bootup process:eek: . Does... (1 Reply)
Discussion started by: turbo90awd
1 Replies

3. UNIX for Advanced & Expert Users

bootup script

Hello there I need to run a script whenever i reboot or startup my HP-UX server. This script adds some routes to the route table, and it start third party aplications like "Star Manager". I thought i could do this simply putting the script in "/sbin/init.d, and a link to the script in... (7 Replies)
Discussion started by: vascobrito
7 Replies

4. UNIX for Dummies Questions & Answers

Bootup Error

Hi all The following error was displayed when a sco server (5.0.5) was booted. What should be done to overcome the problem. Replies appreciated. Bios 03.0 0130688 KB memory good 01 processor(s) in system remote console dialing on, please wait connect fail : modem off cpu clock... (6 Replies)
Discussion started by: raguramtgr
6 Replies

5. UNIX for Dummies Questions & Answers

Why not automatic bootup

Evry time I start up my mavhine ,have to type in unix at Boot : Is there a way unix should bootup automatically? Asif (2 Replies)
Discussion started by: asif iqbal
2 Replies

6. AIX

How to start ssh at bootup

Hi i installed ssh of version v 1.21 and my AIX is of 5.3. I want to start my ssh deamon at the startup can any one please help me out reg.. Thanks in advance.. (1 Reply)
Discussion started by: kmalla
1 Replies

7. AIX

File system not mounting at bootup

Hi, I've got a recent problem with 2 file systems on an AIX 5.3 server. The fs's are marked to auto mount at startup and do show as being mounted after a a restart however if you cd to the mount point and 'df -g .' it shows the fs hasn't actually mounted. $ mount |grep SQLT0001.0 ... (2 Replies)
Discussion started by: m223464
2 Replies

8. UNIX for Advanced & Expert Users

system slows after bootup for some time

Hi, I am using a Linux system running at run level 3. I am finding a wired problem, once the system boots, the system terminal slows down, I need to type the characters repeatedly to enter my login and password info. Also running any commands takes time, it stays in this condition for some... (1 Reply)
Discussion started by: cjjoy
1 Replies

9. UNIX for Dummies Questions & Answers

bootup sequence

What is the boot up sequence in UNIX? (2 Replies)
Discussion started by: karthi_g
2 Replies

10. Solaris

Sunfire X4600 Errors on Bootup

Hi Folks, Has anyone seen these errors on bootup. Mar 15 12:22:30 svc.startd: svc:/system/device/local:default: Method "/lib/svc/method/devices-local" failed due to signal SEGV.ht (c) 1983, 2010, Oracle and/or its affiliates. All rights reserved. Configuring devices. ... (1 Reply)
Discussion started by: ESSTEAM
1 Replies
BOOT(8) 						    BSD System Manager's Manual 						   BOOT(8)

NAME
boot -- system bootstrapping procedures DESCRIPTION
This document provides information on using common features in the NetBSD boot loader. Additional information may be found in architecture- specific boot(8) manual pages. In the native NetBSD boot protocol, options are passed from the boot loader to the kernel via flag bits in the boothowto variable (see boothowto(9)). Interactive mode In interactive mode, the boot loader will present a prompt, allowing input of these commands: boot [device:] [filename] [-1234abcdmqsvxz] The default device will be set to the disk that the boot loader was loaded from. To boot from an alternate disk, the full name of the device should be given at the prompt. device is of the form xd [N[x]] where xd is the device from which to boot, N is the unit number, and x is the partition letter. The following list of supported devices may vary from installation to installation: hd Hard disks. fd Floppy drives. The default filename is netbsd; if the boot loader fails to successfully open that image, it then tries netbsd.gz (expected to be a kernel image compressed by gzip), followed by netbsd.old, netbsd.old.gz, onetbsd, and finally onetbsd.gz. Alternate system images can be loaded by just specifying the name of the image. Options are: -1 Sets the machine-dependent flag RB_MD1 in boothowto. -2 Sets the machine-dependent flag RB_MD2 in boothowto. -3 Sets the machine-dependent flag RB_MD3 in boothowto. -4 Sets the machine-dependent flag RB_MD4 in boothowto. -a Sets the RB_ASKNAME flag in boothowto. This causes the kernel to prompt for the root file system device, the system crash dump device, and the path to init(8). -b Sets the RB_HALT flag in boothowto. This causes subsequent reboot attempts to halt instead of rebooting. -c Sets the RB_USERCONF flag in boothowto. This causes the kernel to enter the userconf(4) device configuration manager as soon as possible during the boot. userconf(4) allows devices to be enabled or disabled, and allows device locators (such as hard- ware addresses or bus numbers) to be modified before the kernel attempts to attach the devices. -d Sets the RB_KDB flag in boothowto. Requests the kernel to enter debug mode, in which it waits for a connection from a kernel debugger; see ddb(4). -m Sets the RB_MINIROOT flag in boothowto. Informs the kernel that a mini-root file system is present in memory. -q Sets the AB_QUIET flag in boothowto. Boot the system in quiet mode. -s Sets the RB_SINGLE flag in boothowto. Boot the system in single-user mode. -v Sets the AB_VERBOSE flag in boothowto. Boot the system in verbose mode. -x Sets the AB_DEBUG flag in boothowto. Boot the system with debug messages enabled. -z Sets the AB_SILENT flag in boothowto. Boot the system in silent mode. consdev dev Immediately switch the console to the specified device dev and reprint the banner. dev must be one of pc, com0, com1, com2, com3, com0kbd, com1kbd, com2kbd, com3kbd, or auto. See Console Selection Policy in boot_console(8). dev [device] Set the default drive and partition for subsequent filesystem operations. Without an argument, print the current setting. device is of the form specified in boot. help Print an overview about commands and arguments. ls [path] Print a directory listing of path, containing inode number, filename, and file type. path can contain a device specification. quit Reboot the system. In an emergency, the bootstrap methods described in the NetBSD installation notes for the specific architecture can be used. FILES
/boot boot program code loaded by the primary bootstrap /netbsd system code /netbsd.gz gzip-compressed system code /usr/mdec/boot master copy of the boot program (copy to /boot) /usr/mdec/bootxx_fstype primary bootstrap for filesystem type fstype, copied to the start of the NetBSD partition by installboot(8). SEE ALSO
Architecture-specific boot(8) manual pages, ddb(4), userconf(4), halt(8), installboot(8), reboot(8), rescue(8), shutdown(8), boothowto(9) BUGS
The kernel file name must be specified before, not after, the boot options. Any filename specified after the boot options, e.g.: boot -d netbsd.test is ignored, and the default kernel is booted. BSD
September 4, 2009 BSD
All times are GMT -4. The time now is 06:30 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy