Sponsored Content
Operating Systems SCO USB Backup for SCO OpenServer? Post 303044566 by Transpower on Wednesday 26th of February 2020 03:40:52 PM
Old 02-26-2020
USB Backup for SCO OpenServer?

Now that floppy drives are totally obsolete, it's no longer feasible to use CTAR and similar programs to backup and restore an SCO OpenServer installation. So I'm now looking for a simple commercial USB solution. I'd like to image the whole system to a bootable USB and then, if a reinstallation is necessary, boot on the USB and restore the image to the hard drive. Surely someone has software to do this.....
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Help For SCO OpenServer

I've just installed Unix SCO OpenServer System v in an Intel PC and Everithing ok, except just one thing, in the begining of the installation the wizard asked me about the mouse , i have a generic 3 buttons mouse and i took a logitech and did not work i need to change the mouse configuration, ... (2 Replies)
Discussion started by: jimmyvaldes
2 Replies

2. UNIX for Dummies Questions & Answers

sco openserver 5.5

hello! when i try to make my system dual boot with both win98 & sco open server 5.5 it doesn't work at all.neither win98 take start nor sco open server boots.what should i do ? kindly help me thanks (1 Reply)
Discussion started by: buntty
1 Replies

3. UNIX for Dummies Questions & Answers

Openserver 5.07 & APC UPS via USB

I have the latest version of SCO Openserver 5.0.7. I'm trying to install a APC Uninerrupted Power Supply 750EX using the USB port. During the installation it was asking for a port to connect the APC into. The only choices are either tty1a, tty2a, or other. I chose other but it start asking me to... (1 Reply)
Discussion started by: josramon
1 Replies

4. SCO

sco openserver 5.0.7

Dear members when i installed dual processor patch in openserver 5.0.7 in hp ML370 G4 server it hangs in sco at G_hd_config. i tried MP4, EFS 5.64,5.70A but not solved the problem.. (0 Replies)
Discussion started by: M_farooqui
0 Replies

5. SCO

Incremental Backup using TAR in sco Openserver 5.0

Incremental Backup using TAR in sco Openserver 5.0 Dear all I am using sco openserver 5.0. I wanted to take backup of two folder (each 600 MB size) with lot of files. I used to take backup using tar command daily using a script. But the same takes more time. Is there any way to take backup... (0 Replies)
Discussion started by: jamcalicut
0 Replies

6. SCO

SCO 6. Backup & Restore from USB

Finaly got usb working on sco6. If anyone need help with that just ask. My final goal is to able to do a complete system backup/restore to/from usb. The problems I need help with 1. Can't cpio to usb device. Getting an error message device not found 2. When booted from sco6 emergency... (3 Replies)
Discussion started by: miles556
3 Replies

7. SCO

Emergency Help about backup of SCO OpenServer 5.0.7

hi guys im beginner in unix and have many problem with this. i have one old machine that Sco unix OpenServer 5.0.7 installed on it. i wana backup from all partition of hard disk and restore it on another unix machine. how can i do that ? thing like hard to hard for windows !!! i only know how... (1 Reply)
Discussion started by: farzad226
1 Replies

8. SCO

Help about create backup of SCO openserver 5.0.7

hi guys im beginner in unix and have many problem with this. i have one old machine that Sco unix OpenServer 5.0.7 installed on it. i wana backup from all partition of hard disk and restore it on another unix machine. how can i do that ? thing like hard to hard for windows !!! i only know how... (14 Replies)
Discussion started by: farzad226
14 Replies

9. SCO

USB Printing for SCO UNIX OpenServer 5.0.7

Years ago I set up USB printing for SCO UNIX OpenServer 5.0.7 for a client--but I've misplaced my notes on how to do this! Maintenance Pack 5 is installed. I need step-by-step instructions to proceed. I've searched the SCO Knowledge Base site and found nothing there or elsewhere on the Web. (3 Replies)
Discussion started by: Transpower
3 Replies

10. UNIX for Beginners Questions & Answers

Need to end Backup Process SCO Openserver 5

I was attempting to run a backup at our business last Friday evening when I apparently locked up our whole mainframe. Rather than observing the current time and adding a minute or two to that for the backup start time (like I typically would), I accidentally entered the actual current time to the... (11 Replies)
Discussion started by: hometrics
11 Replies
Makebootfat Bootable FAT Disk Creation(1)		      General Commands Manual			 Makebootfat Bootable FAT Disk Creation(1)

NAME
makebootfat - Makebootfat Bootable FAT Disk Creation SYNOPSIS
makebootfat [options] IMAGE DESCRIPTION
This utility creates a bootable FAT filesystem and populates it with files and boot tools. It is mainly designed to create bootable USB and Fixed disk for the AdvanceCD project. The official site of AdvanceCD and makebootfat is: http://advancemame.sourceforge.net/ OPTIONS
-o, --output DEVICE Specify the output device. It must be the device where you want to setup the filesystem. You can use the special "usb" value to automatically select the USB Mass Storage device connected at the system. This option is always required. -b, --boot FILE -1, --boot-fat12 FILE -2, --boot-fat16 FILE -3, --boot-fat32 FILE Specify the FAT boot sector images to use. The -b option uses the same sector for all the FAT types. The other options can be used to specify a different sector for different FAT types. The FAT types for which a boot sector is not specified are not used. This option is always required. -m, --mbr FILE Specify the MBR sector image to use. If this option is specified a partition table is created on the disk. Otherwise the disk is filled without a partition table like a floppy disk. -F, --mbrfat Change the MBR image specified with the -m option to pretend to be a FAT filesystem starting from the first sector of the disk. This allows booting from USB-FDD (Floppy Disk Drive) also using a partition table generally required by USB-HDD (Hard Disk Drive). The MBR image specified with the -m option must have executable code positioned like a FAT boot sector. You can use the included 'mbr- fat.bin' file. -c, --copy FILE Copy the specified file in the root directory of the disk. The file is copied using the readonly attribute. -x, --exclude FILE Exclude the specified files and subdirectories in the IMAGE directory to copy. The path must be specified using the same format used in the IMAGE directory specification. -X, --syslinux2 Enforce the syslinux 2.xx FAT limitations. Syslinux 2.xx doesn't support FAT32 at all, and FAT16 with 64 and 128 sectors per cluster formats. This option excludes all the FAT formats not supported by syslinux. Please note that it limits the maximum size of filesystem to 1 GB. -Y, --syslinux3 Enforce the syslinux 3.xx FAT support. Syslinux 3.00 supports all the FAT types and sizes but it requires a special customisation of the boot sector and of the file 'ldlinux.sys'. This option does this customisation without the need to use the syslinux installer if the 'ldlinux.sys' file is copied on disk with the -c option. -Z, --zip If possible force the ZIP-Disk compatibility. It sets a geometry of 32 sectors and 64 heads. It also uses the 4'th partition entry in the partition table. It's required to boot also in USB-ZIP mode. -P, --partition Ensure to operate on a partition and not on a disk. -D, --disk Ensure to operate on a disk and not on a partition. -L, --label LABEL Set the FAT label. The label is a string of 11 chars. -O, --oem OEM Set the FAT OEM name. The OEM name is a string of 11 chars. -S, --serial SERIAL Set the FAT serial number. The serial number is a 32 bit unsigned integer. -E, --drive DRIVE Set the BIOS drive to setup in the FAT boot sector. Generally this value is ignored by boot sectors, with the exception of the FAT12 and FAT16 FreeDOS boot sectors that require the correct value or the value 255 to force auto detection. -v, --verbose Print some information on the device and on the filesystem created. -i, --interactive Show the errors in a message box. Only for Windows. -h, --help Print a short help. -V, --version Print the version number. IMAGE Directory image to copy on the disk. All the files and subdirectories present in this directory are copied on the disk. DISKS AND PARTITIONS NAMES
In Linux disk devices are named /dev/hdX or /dev/sdX where X is a letter. Partition devices are named /dev/hdXN or /dev/sdXN where X is a letter and N a digit. In Windows disk devices are named \.PhysicalDriveN where N is a digit. Partition devices are named \.X: where X is a letter, but some- times \.X: is a disk and not a partition, for example on floppies and on all the USB Mass Storage devices without a partition table. SYSLINUX
To make a bootable FAT using syslinux you must use the -X option for syslinux version 2.xx or the -Y option for syslinux version 3.xx. You must also copy in the root directory of the disk the files: ldlinux.sys The syslinux loader. syslinux.cfg The syslinux configuration file. linux The Linux kernel image (the file name may be different). initrd.img The initrd filesystem (the file name may be different or missing). You must also specify the 'ldlinux.bss' boot sector with the -b option and possibily the 'mbr.bin' MBR sector with the -m option. Both the sector images are present in the syslinux package. For example: makebootfat -o usb -Y -b ldlinux.bss -m mbr.bin -c ldlinux.sys -c syslinux.cfg -c linux -c initrd.img image LOADLIN AND FREEDOS
To make a bootable FAT using loadlin and FreeDOS you must copy in the root directory of the disk the files: kernel.sys The FreeDOS kernel. Remember to use the "32" kernel version to support FAT32. command.com The FreeDOS shell. autoexec.bat Used to start loadlin. loadlin.exe The loadlin executable. linux The Linux kernel image (the file name may be different). initrd.img The initrd filesystem (the file name may be different or missing). You must also specify the FreeDOS boot sectors available on the FreeDOS 'sys' source package with the -1, -2, -3 option. For the MBR you can use the sectors image available on the FreeDOS 'fdisk' source package. For example: makebootfat -o /dev/hda1 -E 255 -1 fat12com.bin -2 fat16com.bin -3 fat32lba.bin -c kernel.sys -c command.com -c autoexec.bat -c loadlin.exe -c linux -c initrd.img image MULTI STANDARD USB BOOTING
The BIOS USB boot support is generally differentiated in three categories: USB-HDD, USB-FDD and USB-ZIP. The USB-HDD (Hard Disk Drive) standard is the preferred choice and it requires the presence of a partition table in the first sector of the disk. You can create this type of disk using the -m option. The USB-FDD (Floppy Disk Drive) standard requires the presence of a filesystem starting from the first sector of the disk without a parti- tion table. You can create this type of disk without using the -m option. The USB-ZIP (ZIP Drive) standard requires the presence of a device with a very specific geometry. Specifically, it requires a geometry with 32 sectors and 64 heads. It also requires the presence of a partition table with only a bootable partition in the fourth entry. You can create this type of disk using the -m and -Z option. Generally these standards are incompatible, but using the -m, -F and -Z options you can create a disk compatible with all of them. To use the -F option, the MBR image specified must follow the constrains: o It must start with a standard FAT 3 bytes jump instruction. o It must have the bytes from address 3 to 89 (included) unused. And example of such image is in the 'mbrfat.bin' file. For example to create a syslinux image: makebootfat -o usb -Y -Z -b ldlinux.bss -m mbrfat.bin -F -c ldlinux.sys -c syslinux.cfg -c linux -c initrd.img image and for a FreeDOS and loadlin image: makebootfat -o usb -E 255 -Z -1 fat12com.bin -2 fat16com.bin -3 fat32chs.bin -m mbrfat.bin -F -c kernel.sys -c command.com -c autoexec.bat -c loadlin.exe -c linux -c initrd.img image Please note that FreeDos has some problems booting from USB. It works only on very few conditions. EXCLUSION
To exclude some files or directories in the image copy, you can use the -x option using the same path specification which are you using for the image directory. For example, if you need to exclude the 'isolinux' and 'syslinux' subdirectories from the 'image' directory you can use the command: makebootfat ... -x image/isolinux -x image/syslinux image COPYRIGHT
This file is Copyright (C) 2004, 2005 Andrea Mazzoleni SEE ALSO
syslinux(1), mkdosfs(1), dosfsck(1) Makebootfat Bootable FAT Disk Creation(1)
All times are GMT -4. The time now is 07:16 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy