Sponsored Content
Operating Systems SCO Sco unix v/386 3.2 problem boot and install Post 302358508 by jgt on Friday 2nd of October 2009 07:17:01 PM
Old 10-02-2009
What prompted you to re-install the operating system? Do you have a DOS boot diskette, will the system boot to an A: prompt? Try the N1, N2 disk combination in another Pentium System, to see if you can get to the initial installation menu, don't go into the hard drive initialization.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

SCO Unix V/386 Help

I'm new in this.. I want to install SCO Unix in a Intel 166Mhz with 1GB HDD. I have the fowllowing disks with labels: -1 disk of SCO Unix System v/386 Operation system Installation. -2 disks of SCO Unix System v/386 Operation system (extended Utilities) -6 disks of SCO Unix System v/386... (1 Reply)
Discussion started by: jimmyvaldes
1 Replies

2. UNIX for Dummies Questions & Answers

Sco Unix V/386

where can i get a boot diskette for my old SCO UNIX V/386 (3 Replies)
Discussion started by: LEO P. CAPARAS
3 Replies

3. UNIX for Dummies Questions & Answers

SCO UNIX System V/386, Release 3.2

I was just wondering if there is a way to recursive grep for something in this version of UNIX... so that I don't have to do it a directory at a time? (1 Reply)
Discussion started by: PBNOSGT
1 Replies

4. Filesystems, Disks and Memory

SCO openserver 5 install problem

Hello all, I'm trying to install SCO openserver 5 on a 2.5 Gig hard drive, and I tried fdisk and a low-level format of the drive. When I insert the boot diskette all seems fine, and it asks me to set the cd-rom and it sees it and reads from it. Well, I'm thinking all is well until right after I... (1 Reply)
Discussion started by: immulett
1 Replies

5. UNIX for Advanced & Expert Users

Error during Sco Unix boot

Hi friends, i am getting the following error while booting my system which has SCo UNIX . ========================= H iinit PANIC: srmountfun-Error 22 mounting of rootdev hd(1/42) cannot dump 40863 pages to dempdev hd(1/41) : Space for only 0 pages. Dump not completed. safe to power off... (3 Replies)
Discussion started by: sveera
3 Replies

6. SCO

sco unix v/386 boot disk

anyone know where I can download or get a boot disk for sco unix v/386? I have an old PC running sco unix v/386 3.2. I dont have an install or boot disk. I need to reset the root password. I have looked all over the internet and cannot find it anywhere. any help would be greatly appreciated.... (5 Replies)
Discussion started by: format
5 Replies

7. UNIX for Dummies Questions & Answers

Sco Opensserver Boot Problem

Just installing 5.0.5 on a DELL OPTIFLEX GX520. Using a 40GB IDE Drive. Installation appeared to work but on rebooting it hangs at the "LOADING KERNEL hd(40)unix.bss Any ideas please (1 Reply)
Discussion started by: farmacy
1 Replies

8. SCO

SCO System V/386 R3.2 V4.0 disk B2 needed

Hi to all! I'm new here. Recently I bought an Olivetti M400/10 with SCO System V/386 R3.2 V4.0 installed, complete with all disks and manuals. Checking the distribution disks however I found that disk labeled B2 was unreadable. Does anyone have an image of this disk? I wish to do a clean... (7 Replies)
Discussion started by: wisechip
7 Replies

9. UNIX for Dummies Questions & Answers

Error UNIX: UNIX SCO release 5.05 system does not boot

UNIX sco release 5.05 system does not boot:cannot open device hd(40)/boot stage 1 boot failure: error loading hd(40)/bootWhat to do? (2 Replies)
Discussion started by: Joaoalpande
2 Replies

10. SCO

Sco UNIX 5.0.6 not boot

hi i have image SCo Unix 5.0.6 and I want transfer on my HP ML350 G5 after Transfer show this message : boot not found cannot open stage 1 boot failure: error loading hd (40)/boot this hp server used smart array E200i and P400 and sco not recognized HDD tanks (7 Replies)
Discussion started by: moein.mojtaba
7 Replies
mkfs_pcfs(1M)															     mkfs_pcfs(1M)

NAME
mkfs_pcfs - construct a FAT file system SYNOPSIS
mkfs -F pcfs [generic_options] [-o FSType_specific_options] raw_device_file The pcfs-specific module of mkfs constructs a File Allocation Table (FAT) on removable media (diskette, JAZ disk, ZIP disk, PCMCIA card), a hard disk, or a file (see ). FATs are the standard MS-DOS and Windows file system format. Note that you can use fdformat(1) to construct a FAT file system only on a diskette or PCMCIA card. mkfs for pcfs determines an appropriate FAT size for the medium, then it installs an initial boot sector and an empty FAT. A sector size of 512 bytes is used. mkfs for pcfs can also install the initial file in the file system (see the pcfs-specific -o i option). This first file can optionally be marked as read-only, system, and/or hidden. If you want to construct a FAT with mkfs for pcfs on a medium that is not formatted, you must first perform a low-level format on the medium with fdformat(1) or format(1M). Non-diskette media must also be partitioned with the fdisk(1M) utility. Note that all existing data on the diskette or disk partition, if any, is destroyed when a new FAT is constructed. generic_options are supported by the generic mkfs command. See mkfs(1M) for a description of these options. raw_device_file indicates the device on which to write unless the -o N option has been specified, or if the -V or -m generic options are passed from the generic mkfs module. See mkfs(1M) for the list of supported generic options. The following options are supported: -o FSType_specific_options Specify pcfs file system-specific options in a comma-separated list with no intervening spaces. If invalid options are specified, a warning message is printed and the invalid options are ignored. b=label Label the media with volume label. The volume label is restricted to 11 uppercase characters. B=filename Install filename as the boot loader in the file system's boot sector. If you don't specify a boot loader, an MS-DOS boot loader is installed. The MS-DOS boot loader requires specific MS-DOS system files to make the diskette bootable. See NOTES for more information. fat=n The size of a FAT entry. Currently, 12, 16, and 32 are valid values. The default is 12 for diskettes, 16 for larger media. h Mark the first file installed as a hidden file. The -i option must also be specified. hidden=n Set the number of hidden sectors to n. This is the number of sectors on the physical disk preceding the start of the volume (which is the boot sector itself). This defaults to 0 for diskettes or a computed valued (based on the fdisk ta- ble) for disks. This option may be used only in conjunction with the nofdisk option. i=filename Install filename as the initial file in the new file system. The initial file's contents are guaranteed to occupy con- secutive clusters at the start of the files area. When creating bootable media, a boot program should be specified as the initial file. nofdisk Do not attempt to find an fdisk table on the medium. Instead rely on the size option for determining the partition size. By default, the created FAT is 16 bits and begins at the first sector of the device. This origination sector can be modified with the hidden option (-h). nsect=n The number of sectors per track on the disk. If not specified, the value is determined by using a dkio(7I) ioctl to get the disk geometry, or (for diskette) from the results of an FDIOGCHAR ioctl. ntrack=n The number of tracks per cylinder on the disk. If not specified, the value is determined by using a dkio(7I) ioctl to get the disk geometry, or (for diskette) from the results of an FDIOGCHAR ioctl. N No execution mode. Print normal output, but do not actually write the file system to the medium. This is most useful when used in conjunction with the verbose option. r Mark the first file installed as read-only. The -i option must also be specified. reserve=n Set the number of reserved sectors to n. This is the number of sectors in the volume, preceding the start of the first FAT, including the boot sector. The value should always be at least 1, and the default value is exactly 1. s Mark the first file installed as a system file. The -i option must also be specified. size=n The number of sectors in the file system. If not specified, the value is determined from the size of the partition given in the fdisk table or (for diskette) by way of computation using the FDIOGCHAR ioctl. spc=n The size of the allocation unit for space within the file system, expressed as a number of sectors. The default value depends on the FAT entry size and the size of the file system. v Verbose output. Describe, in detail, operations being performed. FILES
raw_device_file The device on which to build the FAT. The device name for a diskette must be specified as /dev/rdiskette0 for the first diskette drive, or /dev/rdiskette1 for a second diskette drive. For non-diskette media, a disk device name must be qualified with a suffix to indicate the proper partition. For example, in the name /dev/rdsk/c0t0d0p0:c, the :c suffix indicates that the first partition on the disk should receive the new FAT. For a file, raw_device_file is the block device name returned by lofiadm(1M). EXAMPLES
The media in these examples must be formatted before running mkfs for pcfs. See for more details. Example 1: Creating a FAT File System on a Diskette The following command creates a FAT file system on a diskette: mkfs -F pcfs /dev/rdiskette Example 2: Creating a FAT File System on a Disk The following command creates a FAT file system on the second fdisk partition of a disk attached to an based system: mkfs -F pcfs /dev/rdsk/c0d0p0:d Example 3: Creating a FAT File System on a ZIP Disk The following command creates a FAT file system on a ZIP disk located on a SPARC based system: mkfs -F pcfs /dev/rdsk/c0t4d0s2:c Example 4: Creating a FAT File System on a JAZ Disk The following command creates a FAT file system on a JAZ disk located on a SPARC based system and overrides the sectors/track and tracks/cylinder values obtained from the device's controller: mkfs -F pcfs -o nsect=32,ntrack=64 /dev/rdsk/c0t3d0s2:c See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWesu | +-----------------------------+-----------------------------+ |Interface Stability |Stable | +-----------------------------+-----------------------------+ fdformat(1), fdisk(1M), format(1M), lofiadm(1M), mkfs(1M), attributes(5), fd(7D), dkio(7I), fdio(7I) NOTES
The default MS-DOS boot loader, which is installed by default if -o B is not specified, requires specific MS-DOS system files to make the diskette bootable. These MS-DOS files are not installed when you format a diskette with mkfs for pcfs, which makes a diskette formatted this way not bootable. Trying to boot from it on an based system will result in the following message: Non-System disk or disk error Replace and strike any key when ready You must format a diskette with the DOS format command to install the specific MS-DOS system files required by the default boot loader. You can use lofiadm to create a file that appears to a mkfs command (for example, mkfs_pcfs or mkfs_ufs) as a raw device. You can then use a mkfs command to create a file system on that device. See lofiadm(1M) for examples of creating a UFS and a PC (FAT) file system on a device created by lofiadm. 1 Dec 2003 mkfs_pcfs(1M)
All times are GMT -4. The time now is 03:12 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy