73s de Phreakout. :rambo:Oh, of course...sorry, that my shortsightedness in listing it with the SE/30 when talking about Mode32. The thing is that I am also looking at the Classic II in the event I have trouble finding a decent SE/30. The Classic II really can't go on-line anyway because of the lack of the expansion port for the ethernet card. In addition I don't know how good the TCP/IP is on the really early versions of System 7.0 (if it was supported on the earlier versions). Pretty much if I end up the Classic II route, I know I am probably not going to go on the internet. But with the SE/30 it sure does look like a good possibility.Once you get an SE/30, you'll definitely want Mode32. However, a Classic II only supports 10MB of physical memory (the 2MB on the board + 2 4MB SIMMs) so Mode32 is superfluous for that machine.
If you go the Classic II route, I don't advise trying your luck with System 7.5 - use 7.1 or 6.0.8L or you'll just be torturing yourself.
Try to stick with the SE/30, if you can, only because of the expansion possibilities. When Apple introduced the Mac Classic I and Mac Classic II, they actually took a step backwards and made the machines slower than the previous models before them. Apple built the Classic II to replace the SE/30 at the time and the Classic I to replace both the SE and the Machintosh Plus.
Quoted from MacWorld's Mac Secrets, 5th Edition by David Pogue and Joseph Schorr:
-"The SE shares the Plus’s compact design and 68000 microprocessor, although it runs 15 to 20 percent faster than the Plus."
-"(Macintosh Classic) After releasing increasingly faster and more powerful computers for several years, Apple released a cheaper, more basic compact Classic model, based on the slower 68000 microprocessor, in October 1990. Why this step backward? Apple was attempting to create a truly competitively priced computer, one that would be especially attractive to new users. The stripped-down Classic without a hard drive listed for about $1,000—a new low in complete-Mac-system pricing that would stand unchallenged for nearly a decade.
-"(Macintosh Classic II (Performa 200)) The Classic II is newer than the SE/30, which it replaced in October 1991. To the chagrin of Mac users who loved the SE/30, however, the Classic II handles most processing jobs about 30 percent slower,even though it’s equipped with the same microprocessor. What accounts for the difference? The data path. The Classic II is equipped with only a 16-bit data path between the ’030 processor and the RAM chips, whereas the SE/30 provides a 32-bit data path. In other words, the Classic II can move only half as much data at one time between the computer’s memory and central processor as the SE/30.
When the Classic II was released, it cost about $1,000 less than an SE/30 (which at the time was selling for more than $3,000), making it a good deal despite the slower speed.Now in terms of the file sharing I SHOULD be able to do that even if my other PC's are Windows right?Yeah, basically I would be looking to share files between machines, NOT run programs. I know that probably will not be possible. Ok, so it sounds like setting up an FTP server would be the best route to go for file sharing. How would I do that? This is something I would like to know how to do because I am right now also converting Xbox's and need to do some FTP work for file sharing as well. Thus I can kill two birds with one stone!Well, you'll have the hardware connectivity taken care of, but now you need to make sure that the right System Extensions are installed for networking on your Mac. More pressing, Windows, with exception to Windows NT 3.xx and 4, doesn't translate the Macintosh platform on a Windows machine. So in order for you to see a Mac on the Windows desktop, you'll need to get a software that will do that for System 7.x.x. Timbuktu Pro for Mac and Windows comes to mind (I have the Mac version at home, if you need it) or Windows 3.x.x/4.x.x. Before I go further, I'm talking about file-sharing across your home network, not Internet. Windows uses samba as a means to communicate across local ethernet networks; Macs before OS X use AppleTalk, a totally different language. You'd need to either make all your Macs support samba or all your Windows machines support AppleTalk. Another easier way might be to set up an ftp server and use an ftp software to send and receive files back and forth.This excerpt taken from MWMS, 5th Edition:
Cross-Platform Networking
For communications with PCs, nothing beats a network. You can share files, send e-mail, share printers, and do a host of other activities by sending electrons over thin cables. The biggest cross-platform network on earth, of course, is the Internet. It connects Mac, Windows, UNIX, and other kinds of computers throughout the world, 24 hours a day. Not only that, but the servers—the computers that host Web sites, distribute e-mail, and serve files via FTP—are a mix of UNIX, Windows NT, and (in surprisingly large numbers) Macs. You can’t tell which operating system is running a particular Web site—and as far as you, the Web surfer, are concerned, it doesn’t matter.
The local networks in an office or school are similar in principle to the Internet, and sometime even use the same technology. Most often, Macs and PCs are connected by Ethernet wiring; Ethernet is a cross-platform cabling standard. But although the wiring is the same, the software is different. Macs sometimes get barred from the network fun by network software products that don’t support the Mac. Fortunately, persistence and a little knowledge is all you need to connect to such Windows-only networking schemes.
A Protocol Primer
To get two computers communicating, either for file-sharing, e-mail, or any other task, they have to use the same set of protocols. You can think of protocols as rules of the road—stop on red, go with green—that computers obey when sending data over wires. It doesn’t matter if the computers are Macs, Windows, or UNIX; as long as they’re communicating using the same protocols, they’ll understand each other. If you really want to get your Mac talking to Windows machines, you’ll have to delve into the tech-speak of protocol-ese; here goes.
Protocols come in what you might call layers. At the bottom layer are basic transport protocols that establish communications. On top of that are protocols that provide services—file servers, e-mail service, Web service, remote access service, and so on. Ethernet wires can carry multiple protocols at the same time—which is fortunate, because today’s computers often use different protocols for different tasks. Your Mac might send AppleTalk signals to print, and TCP/IP signals to access the Internet. All that’s necessary for Macs and PCs to communicate is that they speak the same protocols. Here are the most basic transport protocols used today:
■AppleTalk: AppleTalk has been a standard Mac networking protocol since 1984. AppleTalk is the language spoken by network printers; it’s also the protocol used for the Mac’s built-in File Sharing feature (again, see Chapter 35). PCs normally don’t speak AppleTalk—unless you equip them with add-on software.
■TCP/IP: TCP/IP is the most widely used set of protocols in the world—it’s the language of the Internet, and is becoming more and more common on local networks as well. Mac OS, Windows 95, Windows 98, and Windows NT all come with TCP/IP software.
■IPX/SPX: This technical-sounding item is Novell’s set of protocols for its NetWare networking system. Although Novell’s products and customers have been moving towards TCP/IP, the world’s offices are still filled with IPX networks. Macs can participate on NetWare IPX networks using a software kit from Novell called NetWare Client for Macintosh software, which includes a control panel called MacIPX.
■NETBEUI: A common IBM protocol used in DOS and Windows for small networks, NETBEUI was used in such networking products as Microsoft LAN Manager, Windows for Workgroups, IBM PCLAN and LAN Server. If this is what your office uses, you’re out of luck—no software lets Macs communicate via NETBEUI.
Putting PCs on a Mac Network
When adding a few PCs to a mostly-Mac network, it makes the most sense to adopt the PCs to your network rather than the other way around. This usually means adding the AppleTalk protocol to the PCs. You can do this with one of two products for Windows: PC MacLAN (from Miramar) or COPSTalk (from Cops). Both let Windows access Macs that have File Sharing turned on, plus dedicated Mac AppleShare servers. PC MacLAN, in fact, even lets Macs access the Windows machines. PCs running either PC MacLAN or COPSTalk can print to Mac Postscript printers on the AppleTalk network, and Macs can print to any Postscript printers connected to the Windows PCs.
Using an AppleTalk product for a cross-platform network also makes sense if you’re connecting a few Macs and a few PCs together, and your background is mostly Macintosh. Because AppleTalk is a plug-and-play, self-configuring protocol, it’s easier to set up and run PC MacLAN or COPSTalk than to tangle with the products discussed in the next section.
Macs on PC networks
AppleTalk doesn’t make much sense when you want to add Macs to an established PC network. Nor does adding software to a Windows NT server, when it’s just a few Macs in a mostly Windows environment. Instead, you should adapt the Macs by installing special software on them. DAVE (from Thursby) is software that adds a Mac to a Microsoft network using the TCP/IP protocol. Macs thus equipped can log onto standard Windows NT “domains.” To the Mac user, PCs with Microsoft file sharing turned on become visible in the Chooser; you select and log on to them just as you would on a standard Mac AppleTalk network.
DAVE also lets the Macs share their hard drives with the PCs on the network. The PC users can log onto DAVE-equipped Macs just as they would ordinarily log onto other Windows machines. Configuring DAVE on the Mac is usually more complex than Mac networking; some knowledge of PC networking is very helpful. So is Thursby’s manual, which walks you through the set-up procedure. If the existing PC network runs the Novell NetWare networking system, you can add your Mac to the network by installing NetWare Client for Macintosh (or its more recent incarnation, IntranetWare Client for Mac OS). The Macs can use either the Novell IPX protocol or TCP/IP; the client doesn’t interfere with normal AppleTalk functions. For example, you can log into the network server through IPX, browse the Internet using TCP/IP, and print using
AppleTalk. The Novell client software lets your Mac access the Novell Directory Services (NDS) to log into file servers and printer functions.
Connecting to Windows NT Server
Windows NT Server, yet another common Windows-based networking software kit, comes with software called Windows NT Services for Macintosh (SFM). (Although SFM comes on the Windows NT Server CD-ROMs, it must be installed and configured separately.)
Like PC MacLAN, SFM installs on the NT Server, and gives Macs access to the server using AppleTalk. Once you’re hooked up this way, you log onto the NT server through the Chooser, just as you would on an all-Mac system. Unlike PC MacLAN, the SFM file service is one-way—Windows PCs can’t access the Macs on the network.
Macs also use the printers connected to Windows NT servers—sort of. If the printer is not a Postscript printer, then Macs can only print in black and white and at 300 dpi—even if the printer supports color and higher resolutions. On the other hand, SFM has the Microsoft logo on it, which makes it attractive to many of the people who run the networks in today’s companies.Both 8-pin serial ports on the back ARE LocalTalk. Apple just named one of them the Modem port and the other Printer port, since they figured most users will use them for THOSE purposes.Ahhhh, Ok, so they are the same thing then. So then the port labeling really doesn't have that 'fixed' designation, both ports are then serial RS-422 ports.Just remember that the Printer Port is more designated for AppleTalk networking than the Modem Port; this is how Apple has standardized their way of hardware design as far as networking goes.As said before, the serial/LocalTalk/RS-422 ports are fully compatible with RS-232 standards.Can I build a standard interface using parts from RS-422 and RS-232 cables? Usually the controllers I deal with have DB9 connectors and I am wondering if a conversion would be as easy as just making an adapter/wire.Short answer, yes you can. Just make sure you connect the correct wires between the DB9 and Apple's 8-pin DIN plug.SCSI, is a bit faster since it supports up to 1.5 megabytes per second. It has to in order for external SCSI devices to transfer quickly, especially if you have an external SCSI hard drive.I don't think I would be interested in a SCSI external hard drive at the moment, BUT what might interest me is a SCSI CD rom. Then I could burn disks for the Mac.Um, I don't think you can burn CDs under System 6 or 7. Oh, wait. You're talking about using an external SCSI CD-ROM device. Oh, okay. Then, in that case, yes you can. All I can say is good luck trying to burn a CD that's formatted for System 6 or 7 using a Windows machine.
Post #19 by phreakout
| Source Forum | 68kMLA |
|---|---|
| Category | Networking |
| Post Date | Sat, 6 Feb 2010 - 02:29 |
| Original URL | https://68kmla.org/bb/threads/se-30-common-fixable-problems.19764/ |
Post
73s de Phreakout. :rambo: