Sponsored Content
Full Discussion: How do I start a thread ?
Operating Systems SCO How do I start a thread ? Post 302201849 by The_Librarian on Tuesday 3rd of June 2008 09:44:39 AM
Old 06-03-2008
Quote:
Originally Posted by mos8001
I am actually trying to find out the following:
Using MS Windows, XP PRO, I downloaded an Adaptec SCSi 39160 driver from SCO Unix site.
Driver is ad160.btld.
I now need to copy this driver to a SCO Unix 5.5 standalone server, via a floppy diskette.
I've tried SCO505 Diskimage and it didn't have the ad160 file in the image.
I've tried the btld image also. Unix can not find the ad160 driver.
My client needs their server back today. May 7/08.
How can I copy the ad160.btld driver from MS Windows to a Unix floppy.
Thank you in advance.
John
You'll need the RAWRITE program to write the disk images to a stiffy disk.
 

4 More Discussions You Might Find Interesting

1. Programming

How to cancel a thread safely from the initial thread?

how about asynchronous canceling? or with signal? if with signal whether it effects the process? my english so badly :( :( (1 Reply)
Discussion started by: alan.zhao
1 Replies

2. Shell Programming and Scripting

Start program in background (or start crontab ahead of time)

Hey! I'm working on a script that will add a user, create some configfiles, and add a crontab for the user. The crontab looks like the following: @reboot /home/user/program config.conf & I would like for this process to start at the end of my script under the corresponding username by... (0 Replies)
Discussion started by: noratx
0 Replies

3. SCO

SLD: Failed to start the PMD Connection thread. (PM_THREAD_FAILED_TO_START).

Hello, I have a client with an 18 year old SCO Openserver 5.0.5 server. They can't find their installation media. They are experiencing an error at login: *LOGIN: ERROR- Failed to initialize policy manager. (IFOR_PM_FATAL) The status from the policy manager daemon (PMD -... (10 Replies)
Discussion started by: brhunt
10 Replies

4. Emergency UNIX and Linux Support

How do i start a new thread with my android phone?

thanks (6 Replies)
Discussion started by: jgt
6 Replies
mtools(1)						      General Commands Manual							 mtools(1)

NAME
mtools - Provides a collection of tools for manipulating DOS files DESCRIPTION
The mtools commands are a public domain collection of programs that let you read, write, and manipulate files on a DOS file system (typi- cally a diskette) from a UNIX system. Each command attempts to emulate the DOS equivalent command as closely as possible. The following commands are available: Converts a DOS file to UNIX Changes DOS file attribute options Changes or reports the DOS working directory Copies DOS files to and from a UNIX operating system Deletes a DOS file Displays contents of a DOS directory Copies a diskette to another diskette as a bit-image copy Adds a DOS file system to a low-level formatted diskette Creates a shell script to restore UNIX file names from DOS Labels a DOS volume Makes a DOS directory Removes a DOS directory Performs a low level read (copy) of a DOS file to UNIX Renames an exist- ing DOS file Displays the contents of a DOS file Performs a low level write (copy) of a UNIX file to DOS Converts a UNIX file to DOS format DOS file names optionally are composed of a drive letter followed by a colon, a subdirectory, and a file name. Subdirectory names can use either the '/' or '' separator. The use of the '' separator or wildcards requires the names to be enclosed in quotes to protect them from the shell. The regular expression "pattern matching" routines follow the UNIX rules. For example, an asterisk (*) matches all DOS files in place of asterisks separated by a dot (.) such as *.*. The archive, hidden, read-only and system attribute bits are ignored during pattern match- ing. Not all UNIX file names are supported in the DOS world. The mtools commands may have to change UNIX names to fit the DOS file name conven- tions. Most commands provide the verbose option (-v), that displays new file names if they have been changed. The following table shows some examples of file name conversions: ----------------------------------------------- UNIX name DOS name Reason for the change ----------------------------------------------- thisisatest THISISAT file name too long file.stuff FILE.STU extension too long prn.txt XRN.TXT PRN is a device name .abc X.ABC null file name hot+cold HOTXCOLD illegal character ----------------------------------------------- All options use the minus (-) option, not the slash (/) as provided under DOS conventions. The mcd command is used to establish the device and the current working directory (relative to the DOS file system), otherwise the default is assumed to be A:. All the mtools commands return 0 on success and 1 on complete failure. All mtools require a floppy diskette properly installed on the system. All mtools facilities address a device named /dev/disk/floppy, therefore, a symbolic link between the floppy device and /dev/disk/floppy is also required. RESTRICTIONS
If the proper device is not specified (when multiple disks capacities are supported), an error message from the device driver may be dis- played. This message can be ignored. EXAMPLES
If the diskette is a SCSI attached floppy drive designated device rz13, the following example sets up a floppy diskette for access by the mtools commands: # cd /dev # ./MAKEDEV disk/dsk13 You can then link the device to /dev/disk/floppy as follows: # ln -s /dev/rdisk/dsk/13c /dev/disk/floppy The following example sets up a floppy diskette for access by the mtools commands if the floppy drive is FDI attached: # cd /dev # ./MAKEDEV fd0 You can then link the device to /dev/disk/floppy as follows: # ln -s /dev/rfd0c /dev/disk/floppy The following example also sets up a SCSI attached floppy diskette for access by the mtools commands: # /usr/sbin/mknod /dev/rdisk/dsk13c c 8 21506 You can then link the device to /dev/disk/floppy as follows: # ln -s /dev/rdisk/dsk13c /dev/disk/floppy Remember to use the appropriate SCSI name and minor number for your configuration. In this example, this is dev/rdisk/dsk13c. Caution This method is recommended for use only by experienced system administrators. SEE ALSO
Commands: dos2unix(1), ln(1), mattrib(1), mcd(1), mcopy(1), mdel(1), mdir(1), mdiskcopy(1), mformat(1), mlabel(1), mmd(1), mrd(1), mread(1), mren(1), mtype(1), mwrite(1), unix2dos(1) Floppy disk interface: fd(7) Utilities: MAKEDEV(8), mknod(8) mtools(1)
All times are GMT -4. The time now is 05:32 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy