Until I can get BeOS configured for Internet use, I needed a way to move files from Windows to BeOS. I think I found a reasonable solution: I created a Windows partition labeled "BeOS Access" where I can place downloaded files from Windows and access them from BeOS.

My question is, how can I get BeOS to mount this partition only without mounting all of the Windows and Linux partitions? It seems like such a simple thing, but I can't find a control for it anywhere. Any ideas?

Thanks again,
Bob W.

Bob,

Use a boot script to mount the partition. This way, you can selectively mount whichever partitions you want automatically.

By the way, I was wondering what sort of problem(s) you're having setting up BeOS for Internet access. It should only take one or two minutes (no exaggeration here--I'm talking literal 60-second minutes) to configure BeOS networking for Internet access*.

no keys-
* Assuming, of course, your networking hardware (network adapter or modem) is BeOS compatible and your ISP isn't using some sort of weird non-PPP protocol or requiring a host name response for DHCP. Theoretically, complications are certainly possible. I've installed BeOS several times and switched ISPs five times as well, using both dial-up networking and broadband cable Internet access and never run into a problem. Personally, I've found that configuring BeOS for Internet access is *much* simpler than with Solaris, Linux, and even Windows. There's very few settings you have to worry about and best of all--you don't have to reboot, just click the Restart Networking button in Network preferences.

Thanks for replying...

I wouldn't have any idea how to configure a bootscript at this time. I did see a program listed at BeBits that might be what I'm looking for, but the link was dead - I'll keep trying that.

I'm not sure what specific Internet problem I'm having. When using BeOS I get the terminal, click on connect, and absolutely nothing happens. For starters I have an unlisted modem - it's a US Robotics Voice PCI. I have tried each of the US Robotics drivers with the same results. It might just be the driver, but it's odd that I don't see any port choices in BeOS; the Windows Port setting is COM5. - Does BeOS detect the port automatically?

Thanks again for taking the time to reply. If I could get these couple of things figured out, I think I would love BeOS!

-Bob W.

About the boot script:

You can execute any script you want automatically at boot time by putting your script in

~/config/boot/UserBootscript

To make things easy for beginners, BeOS includes a sample bootscript called "UserBootscript.sample". Just remove the ".sample" part to turn it into a real working script (you might want to keep a copy of the original sample).

As for the scripting, you can use any language to write scripts in BeOS—Python, Perl, CGI, etc. You might want to use BASH for most things just to make it easy to exchange scripts with other users and for Linux compatibility, but then again, I guess it doesn't really matter. Whatever you want. The beauty of it is that you've got choices.

BASH* is the shell that comes bundled with BeOS, but you're not stuck with it. Other shells can be ported and are likely already available, so if you're more familiar with or prefer something other than BASH (like C Shell, Bourne, or whatever), it's possible to use a different shell.

If you're just getting started and aren't familiar with any scripting languages at all, I'd personally recommend sticking with BASH--at least to get started. Then again, this is just my personal opinion. Some people might think other scripting languages are better, but a lot of tutorials, examples, user guides, how-to documents, and instructional books use BASH.

Think of UserBootscript as your AUTOEXEC.BAT file. The UserBootscript file acts just like AUTOEXEC.BAT in MS-DOS. However, you can do a LOT more with UserBootscript than you could ever possibly do with AUTOEXEC.BAT, since you can use some pretty powerful scripting languages.

If you want, you can even create a startup folder that functions the same as in Windows.
To make a startup folder:
Make a startup directory. Name it whatever you want. Be sure to put it on your BeOS boot partition so it'll be available to BeOS when it boots. You might want to put it in /boot/home/config. I named mine "autostart”.
To make a startup folder called "autostart" in /boot/home/config, type the following at a BASH prompt:
$ mkdir ~/config/autostart

Add these lines to ~/config/boot/UserBootscript:
for program in /boot/home/config/autostart/*
do
"$program" &
done

Now you can put shortcuts to applications or scripts in the autostart directory and they'll be executed automatically at every boot.

You can also even add scripts to your Be menu.

There's a lot of good information about scripting in BeOS and TONS of information about scripting and BASH in general. You'd be amazed at the things you can do with scripts.

Be sure to check out the Be Tips Server at http://www.betips.net. You're sure to find lots of very helpful information there. There's plenty of useful info scattered all about the 'net, though.

As far as mounting a volume, just use the good ol' BASH mount command with the usual syntax. If you're not familiar with the BASH mount command, try

mount --help

If the help doesn't give you all the information you need, there's tons of information and examples for using mount on the 'net.

As for the Internet connectivity issue(s):

First, what's this terminal you're using? Are you using some sort of Telnet or other kind of terminal emulator?

I can't offer much help regarding the modem; I never use the PCI variety. I'd bet money it's a Winmodem (Nearly all PCI modems are software-based; I am only aware of one "real" modem on a PCI card and it's made by U.S. Robotics.)

If your modem doesn't show up in the Devices list in Preferences, BeOS isn't using it. You can manually add modems, but that's for non plug and play, jumpered hardware modems. Manually adding a plug and play, unjumpered Winmodem isn't going to get you anywhere, 'cause if it were going to work, it would have already been detected and would show up and work.

BeOS should detect or configure modem settings automatically, but...

Software based modems can be problematic.

BeOS modem support was originally limited to real hardware modems--and only external ones at that. Also, modems were ONLY supported on COM1.

A lot of people may suggest not using software based modems and use real hardware modems instead. I'd tend to agree with them, although many people have reportedly had great success using Winmodems under BeOS.

A lot of people may tell you that the modem's COM port setting *must* be set to COM1. It may be theoretically possible to use a different COM port setting, but I have never been able to make this work. I have only been able to get modems to work if they're set to COM1.

I've heard a few people say that internal modems don't work with BeOS. This was true with older versions of BeOS, but it isn't true now. Internal modems work fine as long as they're set to COM1 and are supported. Any real hardware modem will work. Only some Winmodems will work.

Here's what I'd try (in order of preference):

Replace the Winmodem with a hardware-based external modem and set it to COM1

Replace the Winmodem with an internal hardware-based modem and set it to COM1

Boot Windows and use a configuration tool (assuming one was provided or is available) to manually reconfigure your modem (if possible), setting it to COM1, base I/O address 3f8, IRQ 4, reboot Windows to make sure the settings stick, boot BeOS, and try again with the new settings.

I don't think it's a WinModem, it has it's own speaker, etc.

I did change the COM Port to 1, not a simple task either - there is no adjustable setting within Windows 98. Following instructions at www.Dell.com I manually changed the registry.

The new registry settings didn't affect the capability of using the Internet in Windows (obviously, I'm on line right now). But with BeOS there is still nothing at all, not even a click or dial tone. The terminal I mentioned earlier is the PPP Terminal.

Beats the heck out of me. I'm going to be very disappointed if I did get stuck with a Winmodem...

Bob W.

I'd bet a large sum you've got a WinModem.

If your machine was manufactured by Dell, Compaq, Hewlett Packard, Gateway, Packard Bell, or IBM, you probably have a WinModem. Actually, if your computer isn't made by the aforementioned companies, you probably have WinModem. Just about every pre-assembled system these days has a controllerless modem. If it doesn't, I'm sure the sales literature will point it out as a major feature.

Another thing that suggests to me that you've got a WinModem is that the software apparently set the modem to COM5 as a default setting. Many all-hardware modems also allow COM settings above COM4, but it's been my experience that most controllerless and totally software-based modems use COM5 as a default setting.

U.S. Robotics modems report their product code if you if you send them an ati7 command. You can use this product code to look up your modem's specs on USR's Web site.

Here's a few product codes I have for U.S. Robotics WinModems:

3CP5699A
005699-00
001750
001783-00
005683-00
005683-03
005690-00
005698-00
2884

If you launch Hyperterminal, connect to COM1 (or whatever COM port your modem is configured to use), send it an ati7 command, and the modem returns one of those product codes, you've definitely got a WinModem. If the code is different, it might still be a WinModem (I'm not sure how old my product code list is--it may be out of date), but you can look up your *exact* model on the Web.

It's getting REALLY hard to tell whether modems have controllers or not. The fact that PCI modems that aren't WinModems exist complicates things. You often can't simply boot real mode DOS from a floppy and echo AT commands without running a special setup program for PCI modems first, and if it IS a WinModem, well, that "setup program" might also function as a controller!

I hope it isn't, but chances are, it's a WinModem.