--------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: F4200002 Date: 03/27/98 From: FRANK SEXTON Time: 05:33am \/To: DAVE RICHMOND (Read 2 times) Subj: OS/2 Updating Shares -=> /* Quoting Dave Richmond to All */ <=- DR> I seem to recall someone somewhere telling me how I DR> can update my shares on my OS/2 box entire d: drive shared, but when I make a new dir, it DR> isn't shared until I update my access control list ie DR> without having to update the access control list. I DR> think there was something I had to remove DR> somewhere...anyone have any idea what the heck I am DR> talking about? Remove the Share. Recreate the share. When asked if you want to apply the ACL click NO (or Cancel, I forget). Then, go into "Manage Access" and choose to share it for both read and write. This way, no ACL, so you'll never have to "update" it to get it to recognize newly created directories. -Frank (fsexton@ibm.net - http://www.concentric.net/~fsexton) --- Blue Wave/OS2 v2.30 * Origin: Wildcard BBS - Thornton, CO 1-303-252-0491 (1:104/725) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: F4200003 Date: 03/30/98 From: DAVID CALAFRANCESCO Time: 10:00am \/To: THOMAS W. MUELLER (Read 2 times) Subj: installing over a network Thomas W. Mueller wrote in a message to David Calafrancesco: TWM> am 22 Mar 98 um 16:59:04 schrieb David Calafrancesco an Roy TWM> J. Tellason: DC> Trust me, unless you are planning to do hundreds of installs (and if you DC> were I'd sooner use Power Quest drive image) you don't even want to hink DC> about anything but CD installs. TWM> Installing Warp Connect over the network is really straight TWM> forward, since IBM included a program to set up the TWM> bootdisks for the remote station which also acts as a TWM> codeserver for the thin laps client. The only thing that's a TWM> little tricky is if you have two differen network cards. And if the second machine is so similar, then using drive image is an even better alternative. It allows you to copy/clone the first install (after applying all the tweaking you need) to as many additional machines as necessary. Just make sure you have enough licenses available. The copy process for a typical 300mb install is around 10-15 minutes. Figure on saving the install time as well as saving yourself from duplicating all the additional installations of utilities, fixpacks, updates, tweakings, editing the config.sys etc... do it once, clone it and keep a copy for restoring back to your clean install in the future should it be necessary. Dave Calafrancesco, Team OS/2 dave@drakkar.mhv.net ... They got the library at Alexandria, they're not getting mine! --- * Origin: Druid's Grove BBS - (914)/876-2237 (1:2624/306) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: F4200004 Date: 03/30/98 From: DAVID CALAFRANCESCO Time: 10:03am \/To: DOUG NEESON (Read 2 times) Subj: Can OS/2 Warp 4 and Win95 be networked??10:03:5403/30/98 Doug Neeson wrote in a message to anyone!: DN> Can anyone help me and tell me if OS/2 Warp 4 (not the DN> connect version) and Win 95 can be networked and if so how? Warp 4 is a connect version, only 3 came in a non-connect version available. Install netbeui support and use the same group name in win95 as OS2. There are several FAQs floating around the net and a search for "warp win95 network" should locate many of the various web sites with detailed instructions. Dave Calafrancesco, Team OS/2 dave@drakkar.mhv.net ... They got the library at Alexandria, they're not getting mine! --- * Origin: Druid's Grove BBS - (914)/876-2237 (1:2624/306) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: F4200005 Date: 03/29/98 From: MIKE RUSKAI Time: 11:00pm \/To: DOUG REYNOLDS (Read 2 times) Subj: WARP 4.0 Some senseless babbling from Doug Reynolds to All on 03-28-98 23:24 about WARP 4.0... DR> I am going to pickup WARP 4.0 to network my BBS machine to my Win95 DR> machine. question is: is a 486dx4-133 with 28megs of ram decent enough DR> to run WARP 4.0 with a BBS and networking support? You will overcommit, but that'll do just nicely. If it's closet-type BBS machine, then keep all bitmaps off the desktop, and use standard VGA resolution to save RAM. Mike Ruskai SA/AG #1106 thanny@home.com ... Windows for Workgroups: Why crash 1 when you can crash 6? ___ Blue Wave/QWK v2.20 --- Renegade v5-11 Exp * Origin: The Licking Factory - OS/2 in NJ! (732) 815-3146 (1:107/634) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: F4200006 Date: 03/30/98 From: MARK LEWIS Time: 02:41pm \/To: RICH WONNEBERGER (Read 2 times) Subj: valid netbios names RW> *** Quoting Mark Lewis to Rich Wonneberger dated 03-25-98 *** >> pointed out that i must ensure 8.3 naming which i have done to no >> avail... the main reason why i want to save files on the Win95 boxes is >> because i'd like to put the Win95 files i download over there and not >> "risk corrupting my OS/2 box" OB-) RW> Last thing I can think of, are you using 8.3 for any path's?? RW> I would think a longer machine name would be ok if its all RW> text/numeric (no spaces, multi period's. I've had funny RW> prob's with W95 & spaces in the path and/or multi periods (ie RW> filename.ext.duh).. RW> After that, I'm outa ideas.. simple netbios names... only one machine has a '-' (dash) in the name... all names are 8 characters or less, no dots... the target directory is on a Win95 box and is called wintmp... i just tried this again by accessing my own ftp server... choose to download the latest fidonet news letter (definitely an 8.3 name ) and choose to save it on the K:\wintmp directory (K: being the mapped drive on the win95 box) and got a "Unable to write to file" error... i also just noticed that there was a volumn label on that drive... i've removed it and tested again... still failed so apparently the volumn label bug is not part of this oblem... i even tried to save to the root dir on that mapped drive and that also failed... as did trying to save the file to any of the OS/2 boxes... guess i'll just have to remember to go to one of the Win95 boxes to download win95 garb^H^H^H^H schtuff... )\/(ark * Origin: (1:3634/12) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: F4200007 Date: 03/30/98 From: SCOTT FERGUSON Time: 11:13pm \/To: LAWRENCE GARVIN (Read 2 times) Subj: OS/2 Updating Shares Hello Lawrence! Sunday March 29 1998 23:19, Lawrence Garvin wrote to Jeff Dunlop: LG> The prompts I get when creating a new share are as follows: LG> (1) from the "Shared Resources and Network Connections - Properties" LG> dialog box, I click on "Create share..." LG> (2) that opens the "Select a Resource to Share" dialog box, which LG> offers me the option to (a) enter a directory, (b) enter a printer, LG> (c) enter a serial device. I enter C:\ in the Directory field and LG> click on okay. This is where you make the first mistake, you should enter c: and NOT c:\ LG> (3) that opens the "Create a Share" dialog box, which allows me to LG> declare the "Share name", it identifies the "Resource" as the LG> directory I defined in the previous dialog box (in this case C:\), it LG> allows me to enter a "Description", select the number of connections LG> authorized, and makes me click on "Manage access..." because the LG> button is not yet enabled. I click on "Manage access..." LG> (4) that opens the "Manage Access" dialog box, which allows me to LG> select "Basic" access permissions or "Customized" access permissions LG> where "Basic" is selected by default. I click on LG> (5) that pops up a message box declaring "The access permissions have LG> been created." and inviting me to click . I click on LG> (6) that pops up a message box declaring "This directory has LG> subdirectories. Select OK to apply the access permissions to the LG> subdirectories." and inviting me to click or . I click on LG> You should choose cancel at this point and then get back to the screen that allows you to create shares and use the "permissions" pulldown and check out the permissions for the drive letter that you have just shared....it should show (drive) in the window. LG> (7) that pops up a message box declaring "You are about to apply LG> access permissions to the subdirectories. This overrides existing LG> permissions on subdirectories. Select OK to continue." I click on LG> (8) and now the button on the "Create a Share" dialog box is LG> enabled allowing me to complete the creation of the share. LG> I did note that if I select at either (6) or (7), it exits me LG> back out to the "Create a Share" dialog box with an enabled LG> button. LG> Perhaps I should be ing at this point rather than "applying LG> access permissions to the subdirectories"? Sounds like you are almost there Lawrence. Scott --- GoldED/2 2.50+ * Origin: Tech. Support BBS - Tucson-AZ - OS2 - 520-797-9785 (1:300/603) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: F4200008 Date: 03/30/98 From: THORBJOERN RAVN ANDERSEN Time: 12:21am \/To: WILL HONEA (Read 2 times) Subj: Warp 4.0 Hello Will, Saturday March 28 1998, Will Honea wrote to doug reynolds: WH> Only thing that dings my setups - regardless of processor speed and WH> RAM is printer activity. That will take some tuning. Are you using the standard setup (i.e. polling) or have you assigned the printing system IRQ7? That might do the trick :-) Regards, Thorbjoern --- * Origin: ravn@dit.ou.dk (2:237/11.64) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: F4200009 Date: 03/27/98 From: TONY BRADFIELD Time: 01:51pm \/To: TONY_BRADFIELD@TESCO.E-MAIL.COM (Read 2 times) Subj: jokes Tony, can you pass some jokes to me... --- FMailX32 1.22 * Origin: The Rocket BBS -<0191 2686461>- 24hrs (2:256/527) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: F4200010 Date: 03/30/98 From: TONY LANGDON Time: 10:49am \/To: LAWRENCE GARVIN (Read 2 times) Subj: OS/2 <-> Unix file sharing via SMB (SCO 10:49:3603/30/98 It's 25 Mar 98 19:05:26, We'll return to Lawrence Garvin and All's discussion of OS/2 <-> Unix file sharing via SMB (SCO VisionFS) LG> and it's working -great- between my Win95 PC and my SCO box. LG> I also have two OS/2 Warp 4 boxes with Peer-to-Peer networking LG> installed. These boxes are able to 'see' and 'mount' an SMB share from LG> the SCO box; however, when I attempt to write files from the OS/2 LG> box(es) to the SCO box, I get voluminous amounts of write errors, and LG> the files that end up on the SCO box are corrupted beyond recovery. LG> Any ideas? Perchance it is merely some networking parameters on OS/2 LG> that need to be adjusted? Perchance I should be using the LAN Manager LG> Client on OS/2 rather than Peer-to-Peer? I have used Samba under Linux with OS/2, no problems. Are you using Samba on the SCO box? Might be worth looking around in comp.protocols.smb (newsgroup). You might find some good answers there. :-) LG> As a workaround, I've considered 'sharing' the Unix shares via my LG> Win95 machine. There seem to be no problems moving files between the LG> OS/2 and Win95 machines, so I thought I'd 'mount' the SCO share to the LG> Win95 machine, and then share it back out of the Win95 machine to the LG> OS/2 machine. Any thoughts from anybody on that (other than it being a LG> bit inefficient?) Hmm, only way it _may_ be possible if if you have a NFS client for Win 95, and mount the UNIX volumes using NFS, then re-sharing to the OS/2 box. Besides the fact that this may not be possible, resharing depends on how good the nfs client is... ... Unable to locate tagline -- Operator Halted! --- FMail/386 1.02 * Origin: The Bridge - Remote Sysop. (3:635/728.18) --------------- FIDO MESSAGE AREA==> TOPIC: 207 OS2 LAN Ref: F4200011 Date: 03/31/98 From: DOUG REYNOLDS Time: 01:32pm \/To: ALL (Read 2 times) Subj: thanx! to all who replied: thanx for all the networking hints! if WARP 4.0 doesn't run with 28megs, i'll pull my 8 meg chip and put in a 32 meg.. (it'll take me to 52 megs of ram, which should be quite enough!) the maverick # http://www.microserve.net/~mav/ # mav@microserve.net ... Brain: [...../] Brain On Drugs: [\.....] Any questions? --- Telegard v3.09.b17/mL * Origin: the rebel multiline 1X % 3.100Gs % 412/459.7290 (1:2610/38)