I am running Windows 98 SE on the PC side and I have also bought a USB-to-Serial cable.

The USB/Serial cable came with a floppy but Windows 98 SE doesn't seem to know what to do with it. (There are no .exe files anywhere on this disk.)

The software is supposed to make it so that my USB ports can be used as "Com" ports.

Has anybody done this already? Do I even need the software for that cable?

~Manny (just keeps going and going and going....)

Hook the adaptor up before you fire up VPC. Then go into the preferences panel and tell VPC to make the COM1 port be the adaptor. I use the Keyspan USB/serial adaptor. If you don't plug the adaptor in first, VPC won't recognize it.

I did this with DRAS, DSP-60, SDDS and Load500. They all work pretty well. DRAS would hiccup once in a while but that was with the OS 9 version of VPC. OS X may have fixed that. I never took the time to figure it out.

We need more Mac people to do this kind of thing. When I did it, I talked to Dolby Labs and USL. Niether of them had heard of anybody trying this. They all told me the same thing... "You're not SUPPOSED to be able to do that, are you?" I just said, "I'm doing it right now!" I think I heard the sound of a lot of head-scratching on the other end of the phone.

I asked them if they planned to make some Mac software for their equipment. They both told me they don't plan to do it right now but IF they got enough call for the Mac software they might consider having some made.
 

One of the more clever emulators I saw, years ago, was the one Digital Equipment Corp. came up with for the DEC Alpha CPU version of WindowsNT. It would emulate Intel x86 actions, but then recompile the most used bits of code for native Alpha CPU use. Still, it didn't work as fast as having a natively coded Alpha version of the app. In which case, if demand keeps rising, Dolby needs a Mac OS X version of its CP interface software.

Mac OS X does require more performance overhead than OS 9.x. The move up is somewhat similar to the hardware requirement differences between Windows 9.x and WinNT/2000/XP Pro.
 

I've done a simple check and -- just as you said -- VPC recognizes the adapter if it is plugged in before loading VPC; it is not recognized if it is not plugged in first.

The Dolby software, however asks for a "Com" port. How do I address this?

Something else: VPC is asking for a driver for this "USB Device." The adapter cable came with a diskette but none of the files will run...

SER9PL.SYS
SERSPL.INF
SERSPL.VXD

I get a dialog box asking me which application to use to open the file.

What are these file types? The only .EXE file is the uninstaller. Obviously these are PC file types so I cannot load them on the Macintosh side.

I bought the cable at http://www.usbgear.com/usa/item_288.html and it was manufactured by Prolific Technology. Is there a better product to use in conjunction with VPC?

~Manny (always the lowest prices.)

I had a Microsoft two button mouse, but it died, and I refused to buy another one. Now I'm using a Logitech 2 button + scroll wheel mouse which also happens to be cordless, but they also make a non-cordless model. Model # is Logitech M-RM67A. The scroll wheel doesn't work on every single application, but it works on most under both OS9 and OS X.

Frankly, I don't care that much about the right button, but I'll never give up the scroll wheel.
 

Windows shouldn't need to have a driver for the adaptor. The Mac OS should own it. You should be safe in dismissing the dialog box that Windows presents asking you to choose a driver.

Also, try connecting the serial cable from the USB/Serial adaptor to the processor before you run the software.

I can tell you what extensions do.

Under OS 9 and before, extensions modify the system at startup time to handle hardware (drivers) or to add some function that wasn't there before. (Add menu items or alter the interface.) They are all loaded at startup time and stay there until you tell the "Extensions Manager" control panel not to load them. Then you have to restart the computer so that the system will reload, this time without said extension.

This was a major headache that caused a lot of crashes. The ability to load and execute modifications to the system was NOT originally designed into the Mac OS. It was originally a HACK where somebody figured out how to modify the system at boot-up time! After that, every Tom, Dick and Harry would write system extensions to do everything from installing device drivers to make your icons dance on screen. The problem is when you get extension on top of extension... modification on top of modification... you never know what could happen. Most extensions behaved OK. Every once in a while you would get one or more extension(s) that didn't know how to play nice with each other. They would eat up memory, slow the system down and cause crashes for no appearant reason. This is the very reason people used to think the Mac crashed a lot. It's not the computer, or the system software that's crashing. It's all those stupid extensions they are loading. (Or allowing to be loaded without checking first.) OK, so it sounds like I'm blaming the victim but the truth is that, under pre-OS X systems, the user had to be very careful about keeping track of extensions or else face problems with unexplained crashes.

Now, the new OS for the Mac, OS X, doesn't use extensions... OR at least it doesn't use them in the same way. OS X uses something called "kernel extensions". Essentially they have been boiled down to their essence. A kernel extension (.kext) is a piece of code that allows the kernel to communicate with hardware... it's a device driver, or what-have-you. At startup time, the OS goes through the list of .kext files and temporarily loads them. It makes a list of what's available and then unloads them all except for the ones that it finds hardware to match. If at any time the system detects a piece of hardware go on-line or off-line the kernel will attempt to track down what has changed and load/unload the necessary .kext files.
In short, the new Mac OS X uses dynamically loaded device drivers or kernel extensions.

In theory, OS X extensions should not cause crashes. They can, however, bypass the memory protection scheme(s) that the kernel provides against crashes. Normally, if one application crashes, the system keeps it segregated from the rest and shuts it down (or allows you to shut it down) without affecting anything else. IF, on the other hand, some butt-head gets cute and starts mucking around where he shouldn't be, he can make a .kext that will cause crashes. (Kernel panics, actually.) Hopefully, that won't happen. At least not for a while, yet. OS X is still pretty new and a lot of hackers are on the "uphill side" of the learning curve. I guess we'll have to wait and see.

So, does any of this make sense to you?

BTW: I did load the driver software into OS X for my "Keyspan" USB/serial adaptor. I fired up VPC and went into the FILE > PREFERENCES menu. Next to the item "COM1" I selected the driver for the adaptor and everything worked perfectly up to the point where you connect the computer up to the processor. I don't have a processor handy so I can't tell you much more.

Windows didn't ask for a device driver and didn't even notice that the COM1 port wasn't even a real port, but a virtual port created for it out of the Mac USB port and associated drivers for the Keyspan adaptor.

So, it looks like the software will run under VPC/OSX just fine. Let us all know how well this works! OK!?
 

Until a Mac OS driver exists, Macintosh users should avoid this cable! The manufacturer is "Prolific Technology" and I purchased it online at www.usbgear.com.

FYI, the Windows drivers don't appear to work, either. Windows doesn't seem to know what to do with them (I've double-checked this on a real Windows PC).

So it looks like I will have to buy the adapter that Randy mentioned.

Randy: I would appreciate it if you would direct me to a site that sells the same adapter that you have.

I am going to try connecting to one of the Dolby units without a driver. A lot of things in Mac OS X don't actually need them anyway. I will have to wait to unpack the Dolby units first, though.

I have used it for several different things... Printers, PDAs and cinema processors. The company gives a list of devices they say will work. Of course, our processors aren't on the list. I called them and asked about it. I got their stock answer: "These are the devices we have tested the adaptor with... blah, blah blah..." So, I pressed them on the issue. The woman at Customer Service kicked it upstairs to Tech Support. I got them to tell me that they know the adaptor will work with many serial devices. The "guys" there have used it to connect GPS receivers to USB ports without problems. We chit-chatted about the things I wanted to do and they told me that they saw no reason why it shouldn't work. Again, I got the standard disclaimer, " We only guarantee our adaptor will work with devices on the list." MY experience proves that any device that uses a serial port in the "normal" way will work. I have only had a few minor glitches in all the time I have used it.

With the above disclaimers I would recommend the Keyspan.

VPC works in a similar way with just about everything you hook to the computer... printers modems and even the ethernet connection. It uses a "virtual switch" to route any network connections the way they need to go. I have used Lotus CC:Mail through the virtual switch and out through my AirPort wireless card to the internet connection at the college, finally, to the remote mail server. I was TOLD that we were SUPPOSED to dial directly into the server. It worked perfectly!

And I wasn't even SUPPOSED to be able to run CC:Mail on a Mac!