01-11-2006
You do have programs that convert files from MS-DOS/Windows format to Unix. Check dos2unix on Solaris and dos2ux on HP. However, those are meant to work on ascii files transferred from Dos/Win env to Unix - I dont think that they will be of any help to you with zipped files.
You can of course try using the utilities - best of luck!
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi all,
I've got a corrupted tar file with some filename being like ?a=n is it possible to get them repaired? (1 Reply)
Discussion started by: klintsovi
1 Replies
2. Shell Programming and Scripting
Hello,
Newbie question:
How can I detect a corrupted file from a script (ksh)?
Thank you,
Martin (6 Replies)
Discussion started by: starless
6 Replies
3. HP-UX
Good Day
Our HP box was hacked and the passwd file has been altered,there are only 2 user accounts active,and these dont have any administrative rights.I need to edit the passwd file to correct the su and root entries.
Does any body have any suggestions as to how i can do this with out the root... (10 Replies)
Discussion started by: cantona7
10 Replies
4. UNIX for Dummies Questions & Answers
Hi,
I am new to UNIX, and have recently installed Suse 9.3. I have been experimenting with all of the commands and have somehow managed to modify the default shell of the root user to an invalid file. Consequently I cannot su to the root user as I receive the 'no such file or directory' error... (2 Replies)
Discussion started by: Tony Montana
2 Replies
5. HP-UX
Hello!
Do you know the meaning of...
"crw-rw---- 1 informix informix 64 0x020001 Jan 21 2004 rifxroot"
I don't know what the first "c" means. Furthermor, if I try to copy this file (rifxroot) it appears a message:
"cp: cannot open rifxroot: No such device or address"
I don't... (1 Reply)
Discussion started by: kaugrs
1 Replies
6. Solaris
Hi All
I work on solaris 8, 9 and 10 platforms and have encountered an error which is my wtmpx files appear to be corrupted as all entries contain the date 1970 (the birth of unix).
Now this is obviously not the case, so my query is:
1 - Can the existing wtmpx files be manipulated to... (6 Replies)
Discussion started by: drestarr96
6 Replies
7. Red Hat
Hi,
Unexpectedly i entered wrong entries in .bash_profile for my user which has administrative permissions. So, i am getting errors for every command. I dont have backup file also, so any body can help me how to recover it.
Regards,
Mastan (7 Replies)
Discussion started by: mastansaheb
7 Replies
8. Web Development
140312 13:43:54 /usr/libexec/mysqld: Table './***/phpbb_posts' is marked as crashed and should be repaired
Its mysqld.log in var/log
alot of messages, but before around hour i tried to "repaid table" from within phpmyadmin, but appears it has no effect.. why? How to fix? (1 Reply)
Discussion started by: postcd
1 Replies
9. UNIX for Dummies Questions & Answers
Hi Folks,
While transferring file from FTP software like Filezilla the files gets corrupted.
Is there any way I can check if the recently transferred file is in ASCII and not corrupted. I have tried using file -i filename command which does tell if the file character set is ASCII or binary... (6 Replies)
Discussion started by: Khan28
6 Replies
dosif(4) Kernel Interfaces Manual dosif(4)
NAME
DOSIF - DOS interchange format
DESCRIPTION
The DOS Interchange Format (DOSIF) is the name given to the media format used by the DOS operating system. This format is based upon that
used in IBM PC and PC AT and HP Vectra systems.
Use the and commands to convert files between HP-UX and DOS file formats; see dos2ux(1). Use these utilities to retrieve information from
a DOSIF volume.
The dos*(1) utilities are the only HP-UX commands that can interact directly with the contents of a DOSIF volume. The only other way to
interact with the contents of a DOSIF volume is to use an HP-UX DOS emulation or coprocessor facility such as SoftPC or the DOS Coproces-
sor. The command cannot be used on a DOSIF volume because the operating system does not recognize it (see mount(1M)).
When constructing file names for the dos*(1) commands, start with the HP-UX path name of the DOSIF volume, then add a colon followed by the
file name:
or
This file naming convention is suitable for use only in arguments of the dos*(1) utilities. It does not constitute a legal path name for
any other use in HP-UX applications.
Metacharacters and can be used when specifying both HP-UX and DOS file names. These must be quoted when specifying a DOS file name,
because file name expansion is performed by the DOS utilities, not by the shell. The dos*(1) utilities expand file names as described in
regexp(5) in the section.
By convention, if the HP-UX device name and a trailing colon are specified, but no file or directory name is provided (for example, the
root of the DOS file system is assumed.
EXAMPLES
Example 1
Specify DOSIF file accessed through HP-UX special file
Example 2
Specify DOSIF file accessed through the DOS volume stored as HP-UX file
SEE ALSO
dos2ux(1).
dosif(4)