VOICE Home Page: http://www.os2voice.org

May 2001 [Newsletter Index] [Previous Page] [Next Page] [Features Index] editor@os2voice.org

OS/2 Tips

Editor's note: these tips are from OS/2 users and in some cases can not be verified by myself. Please heed this as a warning that if you are not sure about something, don't do it.

Use whatever reserved IP space you want. As long as it never leaves your LAN, who cares. The only time you will run into trouble is if your ISP is using the same internal space for their backbone to save IP addresses. I want my IPv6!!!

What does matter is that I don't think you can have 10.0.0.0 or 192.168.0.0 as a node on your LAN. (Brandon, wanna check me? I'm replying off-line or I would go lookup the RFCs.) These are the network addresses for 10.0.0.0/255.0.0.0 and 192.168.0.0/255.255.255.0 respectively.

Set your gateway box (probably the one with InJoy on it) to x.x.x.1 and other boxes to x.x.x.2-254. If you have more than 253 machines on the same subnet you need something bigger than a class C.

10.255.255.255 is the broadcast address for the 10.0.0.0 class A and 192.168.0.255 is the broadcast address for the 192.168.0.0 class C, so you can't use those addresses. You don't get to use the network or broadcast addresses so you lose 2 addresses from each subnet.

Warp 4.51: Installed MSOFFICE 4.3 into WinOs2 & tried to run Word.

It failed to start saying I had to "exit windows and load Share.exe" :(((

After some research on the web & some trial & error I found that it was sufficient to put the command: "SUBST C: D:\" in the autoexec.bat. D is my boot drive.

I did not have to have a dummy share.exe anywhere.

You're not doing it wrong, it just isn't finished. There are some INI entries which should be set first. Using regedit2.exe, under HINI_USER_PROFILE there should be an application "Java Plug-in". If not, create it. For this app, create or set the key "JAVA_HOME" to "D:\JAVA13\jre", or where-ever you installed java 1.3 to. Also, I have the app "Java13" with key "USER_HOME" and value as above. When you have made these modifications, reboot your machine and try again.

Ok, I took eCS Preview 3 and grabbed LVM.DLL from \OS2\DLL. It seems to be compressed. Taking this into account, the "translation" from the mentioned VOICE tip goes like this:

"For eCS Preview 3 LVM use this script file (the Bootmanager sector image is at file offset 238D6h)

--- LVM.PAT ------
FILE LVM.DLL
VER 238E3 04
CHA 238E3 00
VER 238E4 01
CHA 238E4 20
VER 238E6 02
CHA 238E6 00
VER 238E8 02
CHA 238E8 00
VER 238EC 0C
CHA 238EC 00
VER 238FE 464154
CHA 238FE 424D20

--- LVM.PAT ------

and run "PATCH LVM.PAT /A" from the x:\OS2\DLL directory. Then run LVM and recreate the Bootmanager.

In general, you will find the start of the Bootmanager code embedded in FDISK.COM/LVM.DLL by searching for the pattern "APJ&WN" and subtracting the value 3 from the offset found. Beware, this pattern might occur several times, only the one with the string "FAT" a few bytes later is the correct one.

Ciao,
Dani

Easy fix. In Netscape.exe there are several instances of "4.61". I used the Graham Utilities Hex Editor to change each instance of 4.61 to 4.73.

Now my bank thinks I use 4.73 and I can now Login with no problem whatsoever.

The other way to do it is to associate with *mp3 instead.

I just followed up a year old bookmark and came across one of Duane Chamblee's always-deep OS/2 tips titled "Dealing with downloaded ZIP files." ( http://duanec.indelible-blue.com/tools/zipfiles.html )

He gives good step-by-step on setting up a desktop object that is associated with ZIP files in such a way that doubleclicking on any file with a .ZIP extension unzips it into a folder all its own, then opens the folder in Icon view for you. Very neat, and it also works as a drag'n'drop target.

It got me thinking, this works so well, so fast, so "OS/2", why not have these for every other type of archive. RAR files are the second most common on my system, so here's what it takes to replicate Duane's method for RARs:

Refer to his page. I don't want to type all that stuff here. Here's what you do differently.

Instead of the UNZ540x2.EXE package he's talking about, get a RAR distribution from somewhere like hobbes: http://hobbes.nmsu.edu/pub/os2/util/archiver/rarx271.exe

Get the package open and put RAR32.EXE somewhere in a directory on your Path.

Do that other stuff with O.CMD, too. Then create a new Program Object, same way, except use this in the Parameters: /c (md %**N & rar32 x -c- %* %**N & o.cmd %**P\%**N)

Do the Associations page for *.RAR, Icon page for UNRAR etc. That's it.

The difference in the Parameters field is because RAR32.EXE doesn't accept extraction commands to a non-existent directory, so we're MDing one to start with. Hit the HELP button while you're on the Create Program settings to learn more about the string handling in Parameters.

O.CMD is going to expect to find the extraction folder on the Desktop, so don't put anything in the Work Directory blank.

This should be possible with any other archive formats, too. WIC (.WPI's unpacker) escapes me, so far. --

Good luck,
Buddy

Standard Warp 4 installation will not 'see' FAT32 partitions. This will shift partition letters making coexistence with Windows 95 impossible.

To perform the installation follow the following steps:

1. Change Installation Diskettes to be able to recognize and access FAT32
   
   1. Download DANIDASD.ZIP and OS2FAT32.ZIP from Hobbes.
      
   2. Delete OS2DASD.DMD from Diskette 1
      
   3. Copy DANIDASD.DMD to Diskette 1 and rename it OS2DASD.DMD
      
   4. Delete FDISK.COM from Diskette 2 (it is not used by Warp 4 installation)
      
   5. Copy FAT32.IFS to Diskette 2
      
   6. Edit CONFIG.X in Installation Diskette and Diskette 1, and CONFIG.SYS in Diskette 1, inserting after ifs=hpfs.ifs the following statement:
      ifs=fat32.ifs
      
2. Refresh Warp 4 Installation CD with a version of FDISK.COM that supportes FAT32
   
   1. Obtain a new version of FDISK.COM (I used the one in FIXPACK 15)
      
      1. Unpack FIXPACK files (I used Simply Fix 4)
         
      2. Find FDISK.CO_ and copy it to a temporary directory
         
      3. Run UNPACK FDISK.CO_ to get FDISK.COM
         
   2. Make an image of the Installation CD in your hard disk (with XCOPY or drag and drop)
      
   3. Replace \OS2IMAGE\DISK_2\FDISK.COM with the new version.
      
   4. 'Burn' the updated image back to a new CD.
      
3. Perform the Installation Procedure as usual
   
   1. Select an installable partition other than the FAT32 partitions
      
4. Rename OS2DASD.DMD to DANIDASD.DMD and modify the CONFIG.SYS BASEDEV statement. Otherwise a new FIXPACK will overwrite the driver.
   

This should work even if the C: partition is formatted as FAT32

Eduardo Vila-Echagüe

We need to keep a record of these somewhere... We had a naming contest to pick the name of the browser. Needless to say, we didn't use any of the names.

Serious names:

1. Big Kahuna
   
2. Blue Thunder
   
3. Bluezilla
   
4. Pathfinder
   
5. Scout
   
6. Voyager
   
7. Warpster
   
8. WarpSurfer
   
9. WebConnect
   
10. Web Explorer Millenium Edition
    
11. WebExpress
    

Silly names:

1. I.E. Doesn't Know How To Browser
   
2. Gamera
   
3. Gonzo-zilla
   
4. Mo' Better Browser (or Mo' Better Blue Browser)
   
5. Mo' Blue Mo' Browsing
   
6. The Sad, Sad Lizard (a.k.a. Blue Mozilla)
   
7. Shempzilla
   
8. Webspace On Demand
   
9. Yamp (Yet Another Mozilla Port)