Login or Register to Ask a Question and Join Our Community


AIX

Transferring files between Windows and AIX

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Operating Systems AIX Transferring files between Windows and AIX
# 8  
Old 01-05-2009
Other options
Are you sure that networking the two is out of the question?
1. You did not indicate the Windows version or pSeries machine type/model. AFAIK, every pSeries model built in the last 10 years or more has a built-in Ethernet adapter. And a Windows PC likely either has one or one can be bought for very little money. Depending on the type of adapters, a cross-over cable or some other very simple physical connection will get these two machines connected. If this is an option, try it first. If you need help with the software configuration of the networking, ask back here.
2. There is also the option of using SLIP/PPP link between the systems using a TTY serial port. It will be slow, but it will work. Each system likely has a free TTY port. The cable you need is called a null-modem cable, and the number of pins and gender on each cable end will vary. If you want more advice on this option, ask back again. The Windows configuration of SLIP/PPP is found here: MS Windows SLIP/PPP FAQ from UNET or here http://www.sics.se/~bg/telos/slipintro.pdf
And the AIX configuration is found here: Asynchronous Point-to-Point Protocol (PPP) Subsystem
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Transferring files to directories

I have a large number of files with file names of the format iv.epoz.hhe.d.2018.028.000000.sac iv.epoz.hhn.d.2018.028.000000.sac iv.epoz.hhz.d.2018.028.000000.sac iv.epoz.hhe.d.2018.029.000000.sac iv.epoz.hhn.d.2018.029.000000.sac iv.epoz.hhz.d.2018.029.000000.sac... (4 Replies)
Discussion started by: kristinu
4 Replies

2. Shell Programming and Scripting

Script for transferring files

Hi Guys, I have to transfer a few files in my system . The commands to be used are as follows . Will it be possible to send the output of the following in the form of a mail . cd /export/home/teja ls -lrt Quote.java* mv Quote.java Quote.java.20121023 cp /tmp/Quote.java . ls -lrt... (2 Replies)
Discussion started by: Ravi_Teja
2 Replies

3. Shell Programming and Scripting

Transferring files from Unix to Windows server

Hi All, I have to establish as connectivity from Unix server(Solaris) to Windows machine and transfer files. We use public key Private key pair to authenticate from Unix to Unix connectivity to transfer the file. How to establish the sFTP connection from Unix to Windows and transfer the... (1 Reply)
Discussion started by: koti_rama
1 Replies

4. AIX

Do I need to configure my local windows to FTP files from local windows to a UNIX AIX server?

Hi Friends, I have this script for ftping files from AIX server to local windows xp. #!/bin/sh HOST='localsystem.net' USER='myid_onlocal' PASSWD='mypwd_onlocal' FILE='file.txt' ##This is a file on server(AIX) ftp -n $HOST <<END_SCRIPT quote USER $USER quote PASS $PASSWD put $FILE... (1 Reply)
Discussion started by: rajsharma
1 Replies

5. Shell Programming and Scripting

Transferring file from Windows server...

Hi, I want to transfer html files from windows server to unix server. Those files also have to be assigned proper permissions. Can u people suggest any ideas for this scenario? Regards, http://www.unix.com/images/smilies/thumb.gifSanthosh (1 Reply)
Discussion started by: Santhosh_Ind
1 Replies

6. AIX

Transferring files from one AIX server to another AIX server in binary mode

Hi, I am a newbie to AIX. We have 2 AIX5.3 servers in our environment, I need to transfer some files in Binary mode from one server to another and some files in ASCII mode from one server to another server. Could you please help me as to how I need to do that? Thanks, Rakesh (4 Replies)
Discussion started by: rakeshc.apps
4 Replies

7. UNIX for Dummies Questions & Answers

Transferring files between Windows and UNIX(AIX)

How do I transfer Plain Text and/or BMP image files between my WindowsXP PC and my AIX 4.1 PowerPC? I have no network or USB options, just a Floppy disk drive and a CD drive on each machine. Is it possible at all? Any help would be gratefully received:) (11 Replies)
Discussion started by: Pennant Man
11 Replies

8. AIX

How to write files from AIX 4.2.1 to Windows?

I'm wanting to write files each night from an RS/6000 running AIX 4.2.1 to a machine in my Windows domain. I have samba set up on the AIX box, and Windows users can happily access the AIX box but am having issues when wanting to write files in the other direction. From searching around the net I... (2 Replies)
Discussion started by: phaedrus
2 Replies

9. UNIX for Dummies Questions & Answers

Transferring hidden files with scp

Is there a way to scp hidden files only ( with regex ) without specifying the name of the hidden files ? Many thanks in advance ! :) (13 Replies)
Discussion started by: matrixmadhan
13 Replies

10. IP Networking

Transferring data to a windows environment using ftp

I need to transfer data from SCO Unix to a windows 2000 or 98 machine. The files are too big for doscp, and I can't get the right programs for transferring via kermit. So the next step, though perhaps more difficult, would be to set up an ethernet network and tranfer the data using ftp. I have... (3 Replies)
Discussion started by: ccs8217
3 Replies
Login or Register to Ask a Question

LEARN ABOUT DEBIAN

makebootfat

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)