VOICE Home Page: http://www.os2voice.org
We scan the Web, Usenet and the OS/2 mailing lists looking for these gems. Have you run across an interesting bit of information about OS/2 or eComStation recently? Please share it with all our readers. Send your tips to email@example.com. If you are interested in joining a particular OS/2 mailing list, check out the VOICE Mailing List page for subscribing instructions for a large variety of existing lists - http://www.os2voice.org/mailinglists.html.
Editor's note: these tips are from OS/2-eComStation 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.
- Make certain you reboot between every card install.
- One thing I have noticed with audio drivers is the following. Developers of audio drivers take source code from the IBM DDK. They also leave the file audfiles.scr untouched that comes with the example source code. The file audfiles.scr is used by minstall to copy files to your hard disk. In MMOS2\DLL there are two files genin.dll and geninmri.dll. I have understood that genin.dll and geninmri.dll are overwritten because on Warp 3 there is bug in one of these files. For Warp 4 and higher this is wrong. I talked to the developer of this code recently (he no longer works for IBM). He gave me a 100% yes that this is wrong to do on Warp 4(!) and higher.
When installing an audio driver look at the file audfiles.scr and check the for two lines containing the filenames genin.dll and geninmri.dll. DELETE these two lines. Change the amount of files to be copied with -2.
The OS/2 DASD drivers don't really rely on your system BIOS for the drives geometry -- OS/2 queries the drive for this information directly, and communicates directly with the drive interface for I/O (that is, assuming you're running either IBM1S506.ADD or DANIS506.ADD for EIDE based drives, or the proper SCSI controller driver for SCSI drives). These drivers don't use your system BIOS for disk access, thus the BIOS is almost meaningless.
If you happen to be running the IBMINT13.I13 driver however, you will be bound by your BIOS, as this driver uses BIOS calls for all disk access. This is the most primitive, slowest driver however, and in all my years of maintaining OS/2 systems, I've only seen one case where it was necessary (and that was with a special, non-standard IDE card that had 8MB of hardware cache onboard and no specific OS/2 driver), so chances are you aren't using this driver, and thus don't have to worry about this scenario. If you are using this driver however, having a new BIOS may not be of much use for a drive so large -- this driver has rather small size limits IIRC -- much smaller than 40GB.
Regardless, you shouldn't need a new BIOS in order to use your new drive. The only effect your BIOS will have (assuming you're not using the I13 driver) is in regards to the maximum size of your boot partition. If your 1997 BIOS doesn't support LBA, then you may be limited to 512MB for your boot partition. If it does support LBA, you'll be limited to 8GB on your boot partition. If you partition your system correctly, and install core OS/2 portions to other partitions whenever possible/necessary, you should be just fine without having to change your BIOS chips (which may be problematic anyhow -- the system BIOS is generally motherboard specific, containing microcode for the specific mother board design).
PRIMGFIX ftp://hobbes.nmsu.edu/pub/os2/system/patches/warp_4/primgfix.zip Fixes the inherent Warp 4 problem of being unable to permanently associate a "default OPEN" image viewer program other than IBM's Image Viewer with image files. After applying the fix, you can once again associate any program (e.g. PMVIEW) with images so that the program of your choice gets launched from a double-click on the image file.Another solution, according to Klaus Staedtler, another solution is provided by PMView:
In the PMView directory you'll find 'makdefv.exe' execute it.
It already does :-)
Just press shift.
This can also be assigned a hotkey via
View->Preferences->"Shortcut keys" tab,For "Category", choose "File",
You will find a template for "Setup String" in your XWP folder. You drag one off the template and set up the string to be applied to object which are dropped on it. (See XWP User's Guide for more info.)
I have one set up with NODELETE=NO so I can drop "undeleteable" objects on it and make them deleteable.
Sigh. Indeed they did. Beta 45, RC1, and the GA are all like that. Here it only happens when having TV output enabled, so if you don't need that, you can disable it in WarpMedia's MGL options.
There's a new GATV.DLL in our testcase dir that fixes half of the problem. i.e. it can switch to fullscreen with TV output enabled, but not back again. :)
So try to look for an Bios update as the problem is very likely the not properly setup IRQ in the PCI infos. And if there is no complaints sent to ASUS, it is definitely their fault.
Yes. Here is what Innotek says to do: To enable sound in VPC/2 guests:
-Add the following new key:
-Under this key add a DWORD entry named "DisableAudio" and set the value to "0"
Oliver Stein of Innotek found a free, for home use, lpr daemon at: http://www.bio.ukans.edu/Win95-98/instlpr.exe
Those of you planning to use a Doze 9x VPC might want this. It works.
On the CD you have \CID\TCPAPPS\PCOM* files. Unzip all in a temp directory and run INSTALL.
Put a /V after lines 1,3, and 4 from above and watch on the reboot. It should tell you if it is loading the drivers or not. Lets make sure. Also, you should have a few listings in your Hardware for USB if the drivers loaded correctly.
Make sure that USBPRT.PDR and USBPRT.HLP are in \os2\dll
Make sure that you have a USB port listed and selected on the properties of the printer. Mine has a USB icon and the name of my printer ("HP_DJ_930C_1" actually) before I even installed the printer. I don't think having the printer on and/or plugged in matters.
Make sure that usbmon.exe is in \os2.
Make sure there is an object in the Startup Folder, "USBPRT Auto monitor" that calls USBMON.EXE and has parameter USBPRT
This last part is bit scary and I got it from the readme, but, "OS2SYS.INI file must contain USBPRT key with the value D:\OS2\DLL\USBPRT.PDR for the application PM_PORT_DRIVER." -- paraphrased. The bonuspack stuff comes with INITools which has INIeditor.
Some new stuff has dropped recently, so I thought I would tell everyone.
- New mail sounds are supported. To hear a WAV when you get mail, add this to your prefs.js:
You can also use a file:/// URL. This value MUST be a URL, not just a path name.
- We added an icon decoder, so if you browse local directories, you will get icons. This was causing some crashes for some people when downloading - should have that fixed soon.
- Fullscreen mode for OS/2 is in - press F11
- We have fixed the code that was breaking the multimedia plugins. You should now be able to use NPOS2* with Mozilla. Also, I tested QuickFlick and it appears to be working now as well.
- We've done lots more work on printer settings, so it should be querying the settings from the printer now.
I seem to have found out some answers to my questions myself.
Both ECS and Warpv40, contain in their drive:\os2\install directories, the PCMCIA.TBL dat files, which show the contents of the window when installing PCMCIA drivers.
So far I've copied the line for INTEL PCIC from Warp to the ECS dat file, and it does show up in the install window. Tomorrow, I will install the required drivers.
You can disable it completely (preferred). OS/2 System setup -> System -> Logo -> none
The database file format hasn't changed. So it should be possible to just copy the DATBAS_?.INI files between several WarpIN versions.
[Previous Page] [Newsletter Index] [Next Page]
VOICE Home Page: http://www.os2voice.org