Appletalk 6.0.5 / 9.1 Issues

[equant]

Using ethertalk, I can share a folder on my iBook running 9.1 with my SE running 6.0.5, but when I use the same SE to connect to a folder on an iMac running a very fresh install of 9.1, the SE crashes. Anyone have any ideas about why this would be?

I was doing all of my mac development on the iBook, but want to switch over to the iMac so I can use a LCD monitor and use less desk space. I didn't think it'd be an issue, since they have the same OS version, but I've run into this, and a few apps that won't run on the iMac but will on the iBook. Odd.

Thanks for any ideas/help.

Nathan

 

[Charlieman]

I've discovered this recently with various versions of the AppleShare 2 client (as found in your version of System 6, and hackable onto older versions of the Mac OS). It is a new problem to me. For many years I have used System 6 and earlier clients to talk to different AppleShare servers (Mac OS 9.x, Windows 2000 Server SFM, Server 2003 SFM) without problem.

After installing bigger disks in various servers, I have experienced unimplemented trap errors on the same clients. The server is detected in the Chooser, a selection of shared volumes are offered, but the Mac crashes when one is selected. I suspect that this is because the free space or volume size is too large for the AppleShare 2 client implementation on System 6. I have not experienced problems when using System 7.1 with the same servers.

More investigation is required -- I haven't tried System 7.0 and the possible AppleShare client options, for example. If anyone wishes to experiment, contact me for a chat.

 

[Dan 7.1]

is there a way to possibly designate a single folder under os9 on the ibook as the only shared folder? that might clear up any "too much information crashes"

 

[equant]

is there a way to possibly designate a single folder under os9 on the ibook as the only shared folder? that might clear up any "too much information crashes"

Yes, you can do that. It doesn't fix the issue.

 

[equant]

The server is detected in the Chooser, a selection of shared volumes are offered, but the Mac crashes when one is selected. I suspect that this is because the free space or volume size is too large for the AppleShare 2 client implementation on System 6.

Yep, that's exactly what's happening to me. Your theory makes sense to me.

I'll create a small partition on my iMac and see if I can have a shared folder in that.

Nathan

 

[equant]

... Which leads me to the question, what's the best way to partition an existing system disk under 9.1?

For some reason, I thought I could do it with Drive Setup, but it doesn't seem to be the case.

Thanks,

Nathan

 

[tomlee59]

If you mean a utility to repartition on the fly (i.e., keeping all of your data intact), you will need a third-party utility.

If that's not what you mean...Drive Setup will certainly allow you to partition your drive, but you will need to boot off of another disc/k. Setup is smart enough not to allow you to repartition the boot volume while the latter is mounted.

 

[equant]

If you mean a utility to repartition on the fly (i.e., keeping all of your data intact), you will need a third-party utility.

yes, on the fly. Does anyone have any recommendations?

 

[equill]

I have read, in passing, about utilities to permit on-the-fly repartitioning of drives. My inclination is that there is too much at stake to use one of them. If your need is only to transfer files from time-to-time, you can surely consider a permanent small volume for the purpose. Your difficulty may be in 'archiving' and restoring your present OS 9.1 drive if you do not have a suitable external storage volume.

If that should be the case, why not make the iMac the client to the SE's server? The iMac (ie, OS 9.1) should have no trouble with a drive the size of any likely drive in an SE, and the doubt is only whether the iMac can dial-up the SE. This should be quickly testable, and even kludgeable, in extremis.

My SE/30 (System 7.5.5) has no trouble in mounting a 10GB drive from one of my 5500s (G3/400MHz, OS 9.1). I know that an SE/30 is not an SE, but my only current System 6.0.8 machine is having a Dove SCSI card installed at the moment, and is spread over the dining-room table. Similarly, the 5500 has no trouble in mounting both partitions of the SE/30's 4GB drive at once. You have nothing to lose but your composure, so why not try the reverse connection?

de

 

[equill]

Doubled post expunged.

de

 

[equant]

You have nothing to lose but your composure, so why not try the reverse connection?

I don't know how to setup system 6 as an Appleshare server. Am I right that it doesn't come with that ability, I need to add it? I guess I'll go poke around system 6 heaven or Gamba's site and see what I can come up with.

thanks for the help.

Nathan

 

[equill]

Even the longest journey begins with the first step. Much joy to you.

de

 

[equant]

Success.

I created a 735 MB volume on my iMac, and the SE was able to see it and write to it.

I shudder to share how I created the volume since it's sort of a particular solution, but in case someone cares....

I didn't want to lose the data/system I already had on my iMac's drive, but I knew that the end of the volume was empty and unused since it was a pretty fresh install (and large disk), so I skipped defragmenting the drive.

[1] booted a debian linux ppc install disk, exited to shell when I could.

[2] ran 'parted' on the iMac drive

[3] resized the mac partition, and created a new small partition with the free space at the end of the drive.

[4] rebooted with a Mac OS install disk

[5] using the apple disk utilities app, under the preferences menu made the new volume 'mounted at boot time'

[6] rebooted (original system on hd)

[7] The system asked if I wanted to initialize the volume, and I did.

[8] ta-da!

 

[Charlieman]

Ten out of ten for bravery, Equant. I wonder if a similar sort of procedure might be achieved on an Intel Mac using the BootCamp installation utilities? Possibly use BootCamp to perform steps 1 to 3 (ie shrink the existing disk, create a new partition). Then use Disk Utility under OS X to convert the second partition back to HFS+.

 

[equant]

Lol, thanks Charlieman, and thanks for your original hypothesis. I don't know anything about OSX, so I can't ponder your post.

And as a further note about the appleshare limit...

From my real world results it looks like the appleshare volume size limit for System 6 is somewhere between 3 and 10 gigs. Sooo, I'd have to guess that the real limit is either 4096 MB or 8192 MB since those would correspond with 36 and 37 bits.

Also, I've been able to access/read files on a 3 gig volume from system 6, but not write to it (as discussed in a different 68kmla thread), so I guess three's a lower limit for being able to write to the volume.

 

[Anonymous Freak]

Ten out of ten for bravery, Equant. I wonder if a similar sort of procedure might be achieved on an Intel Mac using the BootCamp installation utilities? Possibly use BootCamp to perform steps 1 to 3 (ie shrink the existing disk, create a new partition). Then use Disk Utility under OS X to convert the second partition back to HFS+.

Yes, that works just fine. But you can't expand the main partition back that way, since Disk Utility can't enlarge partitions, and Boot Camp Assistant (which can expand it,) doesn't see the partition anymore.

 

[equant]

Yes, that works just fine. But you can't expand the main partition back that way, since Disk Utility can't enlarge partitions, and Boot Camp Assistant (which can expand it,) doesn't see the partition anymore.

It'd be easy enough to pull the second partition back into first using fdisk or parted (off of a linux/bsd install/recovery disc) if you needed, but I don't know what OS9 or OSX would think when it saw the drive.

Nathan