A1200 networking

[darksun9210]

Assuming you have all the hardware, the pcmcia card, the network etc...

first thing you need is a copy of miami, and a copy of cnet.device in devs:networks.
you should be able to find a copy of miami off of aminet.
even on an unexpanded A1200 with hard disk and pcmcia network card, you'll still have 6-900k of ram left after running the TCP/IP stack. enuff to run an FTP client program also from aminet (about 80k).

set the PC up with static ip address (192.168.0.1)
a static netmask (255.255.255.0)
and if it has access to the internet set the gateway to itself (192.168.0.1)

you can run DHCP, but you need to run a DHCP server on the PC. ok, its easier, but if you are going to run samba, its a pain to deal with. so stick with static addresses if you can

on the amiga, run miami, and set the device to cnet.device and the unit to 0
set the hostname to whatever you want the amiga called on the network (A1200)
set the IP address to static - 192.168.0.2
the netmask to static - 255.255.255.0
the gateway to static - 192.168.0.1 (the PC's address if you want to access the internet through the PC)

these are the basics you need.
you should now be able to get miami online and from the PC, ping the amiga and get a reply. (in a command window type "ping 192.168.0.2") this shows its alive on the network.

on the PC, download an FTP server. i'd recommend WS_FTP server for ease of use. just install and run. piece of cake.

now on the amiga, run your FTP client (probably command line based) and you should be able to connect to the pc, browse and get/put files to and from the PC disks.

samba is a package that allows non-windows machines to be visable and useable on a windows network, you can browse/mount your amiga's drives from the PC's network neightbourhood, and mount the PC's drives on the amiga, set up file share access, user areas, print from the amiga across the network to the PC's printers, mount PC cdroms....

details can be found at www.amigasamba.org.

on an unexpanded A1200, i could mount the PC's drives, but not browse the amiga or mount its drives (only 370k ram left) samba is quite memory hungry. plus i only got a tranbsfer rate of 100k per second over FTP. an accelerated amiga or more ram would get much better xfer rates.

anyone wanna sell a blizzard 060?

[darksun9210]

oh cool. did you setup the netbios stuff in your TCP/IP stack? or just start the TCP stack without it? i used smbfs to mount drives as didn't have much ram left. i don't start samba, but miami has the netbios services setup, and those point to various programs in the samba bin dricetoy.

i have a feeling that as soon as the PC detects the netbios services are there from another machine, it starts to interrigate it about what shares and stuff it has available, as memory drops alarmingly. (64k!) but then jumps again to 600-700k, as i guess the samba services failed to start due to lack of memory and unloaded themselves....

the PC can see the amiga in the win2k version of network neighbourhood, but can't see the shares (memory again). i have managed to get the samba web admin working across the net if i switch off IE explorer loading the images lol
2Mb ram. its almost laughable now. but a GUI multitasking os, tcp/ip stack and web server in 2mb ram. well happy

[darksun9210]

@PiR

netbios stuff. i just followed the samba guide for adding netbios services into Miami to allow the PC to mount the miggys drives. didn't do anything to the PC
but hey it works, :-)
and yeah, its a damn site better than floppies :-D

and on an unexpanded A1200, you count every kilobyte ;-)
and ftp from the miggy to the PC when pulling across samba.lha reported xfer rate of 100.6KB/s which did me fine