Which MiamiDX? AmiTCP?

[matthey]

Hi, I've managed to access my PC share using smbfs from a shell prompt.
 
But now I don't know which file to put this command line in so that it opens up every time I connect to the internet with genesis.
 
Does anyone know if genesis has a startup file it executes when it fires up?

Yes, it does. In Genesis Prefs, Select "Options" on the left and then the "Execute" tab on the top. Edit the "Startup" command as needed.

The Genesis Startup command or an IconX is smart because it won't interfere with games or slow down your booting like the S:User-Startup option.

[matthey]

Ah that would be perfect, but for some reason the Genesis Prefs won't fire up.

You can also access the Genesis Prefs from Genesis in the Menu "Settings->Genesis". Perhaps you are missing a font, Reaction/ClassAct Gadgets or you are low on memory? I have a smaller Genesis Prefs that will save about 20k of memory if you are low.

The Genesis icons are non-standard. If you save the settings, the icon may turn into a small white dot. This can be avoided by loading the icons into SYS:Tools/IconEdit to convert them and then save them. The latest AmigaOS 3.9 Unofficial Boing Bag also has a fix for this.

I'll try running it from WB3.1 disks, see if that works.

It probably won't. The Reaction and ClassAct gadgets are not completely compatible and AmigaOS 3.9 has some new ones. An installation problem may be part of your problems running Genesis Prefs under AmigaOS 3.9.

[matthey]

I try running from Shell and it says.. could not open muimaster.library (ver11)
 
It's funny because I've only just installed OS3.9 with Boing Bags 1-4, nothing more, and the Genesis came from the OS3.9 disks, so I would have though it'd just work? I'm stumped.

That's odd that a Reaction Genesis Prefs requires MUI but it looks like you need to install:

http://aminet.net/util/libs/mui38usr.lha

Edit: Genesis Prefs does not open the "muimaster.library". It could be a gadget or another tool but you will probably need to install MUI at some point anyway.

[matthey]

Well I managed to create an icon that ran a script to show the drive. But my Amiga just crashes all the time.

I'm running AmigaOS 3.9 with the BoingBag updates, Genesis and smbfs 1.74 and my system is very stable. I will on rare occasion get a crash with Genesis.

Maybe you need to set the stack up in your script for smbfs? My smbfs start script looks like this:

Code: [Select]

CD ""
Stack 32768
Run >NIL: SMBFS Workgroup=HOME Service=//MATT/SharedDocs
EndCLI >NIL:

Notice the Stack 32768. I fixed a typo before.

I think I'm going to go back to WB3.1 with ClassicWB, I'm hoping it has much better memory management than OS3.9 stock and hopefully will save me from all the crashing I'm getting right now.

Don't give up yet. It's not the AmigaOS 3.9 memory management.

[matthey]

One more question gents...
I've had to reinstall the OS, because my Amiga was crashing during file transfer.
 
It never crashed when constantly pinging either the Router or the PC, so I'm guessing it's the SMBFS command I've added.

I didn't allocate a stack, I thought stackattack would do that, but I'm not sure.

No sir. StackAttack makes the default stack size larger but it still may not be big enough for some programs. It's unlikely your StackAttack setup provides a 32k stack which is needed by smbfs. StackAttack may no longer be needed with AmigaOS 3.9 and BoingBags as the default stack is increased. Manually setting the stack for CLI launched programs is still necessary though. Workbench launched programs use the stack size in the icon.

What would you recommend for the stack size of the SMBFS command? Bearing in mind I have 2MB Chip Ram and 128MB Fast.

Oddly, I couldn't find a recommended stack size in the documentation for smbfs. Both nicholas (from page 1 of this thread) and I had 32k stacks for smbfs. It's been rock solid for me with that stack size.

stack 32768

I don't know whether it would sit in chip or fast ram?

It should use the highest priority ram that is available first. That should be your fastest fast ram if you have it.

[matthey]

Isn't it just blissful? I'm learning a lot but it does get on my nerves that things don't seem to be stable and work.
 
Are there any of you guys actually using a WIFI card? I don't know whether I'm just best off going to a wired connection?
 
Sometimes it seems to crash and reboot whilst booting, I think it's whilst it's initialising AmiTCP and the prism2v2 drivers, but I'm not sure.

Chances are that the prism2v2 device is not completely stable. I have read that some people have trouble but it could be an older version. I would have stayed with AmigaOS 3.9 as you could then use the newer version of AmiTCP (Genesis). There may be bug fixes that help stability.

I've gave the SMBFS a 60000 stack, just to try and make sure it gets plenty of memory. Was that a stupid thing to do?!? I don't know. I'm just playing around until I can figure it out.

That's ok. Too much stack causes no problems and isn't any slower unless it runs you low on fast memory. There are some tools that will show the amount of stack used. Scout will show the amount of stack allocated and available in real time for all tasks (needs MUI). There are some tools that will track the maximum amount of stack used which is what you really want to know. This amount may change from one program launch to another so it's best to allocate a safe amount of extra stack.

I went for a wired Lan because it's less hassle, I also went with EasyNet because I didn't want to muck around setting up Genesis and SAMBA.  My install took about an hour to setup to a shared drive and is very stable.

I thought Genesis was easy to setup. Smbfs was a little more difficult but not too bad. SAMBA is very difficult. I never got it to work. I was researching my problems when I found smbfs.