VOICE Home Page: http://www.os2voice.org
[Previous Page] [Next Page]
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.
But you HAVE a drive B, even when you don't THINK you do..
Back when there was a single drive system, imaging copying a file from one diskette to another...
So, when you only have ONE drive, since 1981 ALL systems have an A: and a LOGICAL B: drive. copy a:*.* B: reads files from one diskette, prompts to change diskettes and then copies to the new diskette..
There is a command NET COPY That does exactly what you want. It is documented
in the Warp command reference, under the LAN commands.
The rule is:
years divisible by 4 are leap years, except
years divisible by 100 are not leap years, except
years divisible by 400 are leap years, except
years divisible by 1600 are not leap years.
2000 % 400 = 0, 2000 % 1600 = 400; so 2000 is a leap year.
You're hearing one of the things that's likely to be a common Y2K failure mode.
Have you tried temporarily remming out the BASEDEV=PRINT01.SYS statement in config.sys,
rebooting and then trying to delete the file?
What you are experienceing are the "drives" installed by the PC Card
Director software. Look for the ATA PCMCIA driver entry in your config.sys. You
may rem out that line as it adds support for ATA devices such as harddrives. You
may have to play with the entries to rem out the correct lines for your setup.
YMMV, so backup everything before you start playing. The drives you see are "ghosts"
but can cause problems if you are also logging into a LAN. My current network card
(IBM 10/100 CardBUS) requires I suppress the PC Card support on my 770x, so I have
remmed out all of my PCMCIA entries. The temp 3COM card I once used exhibited this
In conclusion, you have not done anything wrong. In fact you have done it all
right. You, and most people just do not need this "feature".
Testing here I found that the issue Vic raises about association of URL and HTM/L
objects with SO5.1 arises if you accept SO5.1's offer to make itself your default
Internet application. I found that if I uninstalled SO5.1 and re-install NC/2 4.04,
the proper association is re-established for the url objects in the web site folders
of Connections. Upon reinstallation of SO5.1 the association with Communicator was
retained. However, I find that there is an apparently hidden association to HTM
objects. Maybe this is a job for Keldar's Association Editor.
Here is my scenerio an what solved the problem for me. I have an aptiva 2137-e26
and had installed the LS-120 and downloaded the drivers and readme files from the
IBM web site. There are (I think) four statements that have to be put in/change
in config.sys. Using the original 'A' drive and these files the Aptiva under Warp
4 recognized the floppy part of the drive as drive B: . Later I decided I wanted
to install a two floppy ( 1.44m and 1.2m) drive unit in the system. I moved the
LS-120 to where the original floppy went and then installed the dual floppy under
the CD rom drive bay. I went into setup and told the system 'A' is a 1.44m and 'B'
is a 1.2m drive. At this point the system wanted to recognize BOTH the LS-120 and
the 1. 2m drive as drive 'B' (what complicated matters more was the vendor who sold
me the dual floppy had pinned it out 180 degrees opposite of normal - good thing
my other computer had one for comparison in it!)
So what is the solution? The readme file gave me the switch I needed:
Modify the statement - BASDEV=OS2DASD.DMD to read:
BASDEV=OS2DASD.DMD /MP:*,1 It works! The drive will then be assigned a higher letter - in my case the drive letter is next to the one for the cdrom drive. Using the new drive letter you will still be able to use the floppy in the LS-120.
boot to command line
type SET DESKTOP=C:\Desktop <- note the drive letter!
If your desktop comes up, then the WP_DESKTOP entry in OS2.INI is missing or
damaged. This REXX script should restore it:
call RxFuncAdd 'SYSLOADFUNCS', 'REXXUTIL', 'SYSLOADFUNCS'
call SysSetObjectData 'C:\DESKTOP', 'OBJECTID=<WP_DESKTOP>'
(Replace "C:" with your boot drive if necessary.)
If that doesn't do it, then possibly the WPS is hung due to garbage in
OS2.INI or OS2SYS.INI. Try renaming them and running MAKEINI to create new
If that doesn't get you a functional (if minimal) desktop, then I'm stumped.
The TCP/IP adapter number does not affect the NetBIOS adapters. Also the NetBIOS
adapter number should be lower NetBIOS/IP adapter number. This is so that NetBIOS
will be tried first. Also, you don't often need both NetBIOS & NetBIOS/IP on
a small network. Choose one and stick with it on all systems. NetBIOS (NetBEUI in
the Micros~1 world) is faster and easier to set up than NetBIOS/IP. On my work computer
I have NetBIOS, TCP/IP and 802.2 (SNA) all on adapter 0 and NetBIOS/IP on 1. The
main reason for NetBIOS/IP, is to get past routers. NetBIOS is non-routable. If
you use NetBIOS/IP, you'll need an RFCNAMES.LST file (similar to the Windows LMHOSTS
file) to map computer names to IP addresses. The reason for the different adapter
numbers for NetBIOS and NetBIOS/IP, is that you can't have two instances of the
same protocol type with the same number.
Both unzip and pkzip have the ability to test zip files for integrity.
unzip -t javaintk.exe
pkzip /test javaintk.exe
are your friends. Also, a simple:
will tell you
will get you the same results.
First: there is the wire (cabling). Here are three factors which are important:
- signalling type: differential, single-ended, lvd (low-voltage differential)Second: protocol standard
- signalling frequency: async, sync5, fast10, fast20 (commonly ultra), fast40 (commonly ultra2), fast80 (coming soon)
- signalling width: 8 (50pin), 16 (68pin) or (VERY seldomly used) 32 (80pin) bit.
- SCSI-1: the very first one. Only usable (ok, the ARE exceptions) for hard drives or tapes. Doesn´t know SCSI_INQUIRE and some commands commonly needed by modern devices. Knows of signalling freq async and sync5.Something special are SCSI-Bridges (First seen on the Adaptec U2W): looks for the controllerchip as if it is the same bus; whereas the bridge allows it to connect LVD-devs on the one side, on the other side standard SE-components. Very special. I prefer two controllers: One doing lvd-things and one for all SE´s; because on LVD-Bus, the command processing is made on LVD-mode too; whereas on standard SE commands always are interchanged in async mode (which increases command overhead and latencies).
- SCSI-2: second version of the protocol. Was needed when more devices were found to need SCSI. Devices have classes and subclasses, removables are possible, signalling freq up to fast20, width up to 32, signal types SE and D.
- SCSI-3: relative new, needed for even more standardisation. AFAIK declares all known signalling types, freqs and width's.
Unimaint is the right thing to use. If you haven't used it before, please be
Start Unimaint > load user ini file > look for application PMMail in the
list on the left > Delete application > close Unimaint
When you next start PMMail, it would have forgotten all about itself in re OS/2,
i.e. its position on the desktop, which printer it prints to etc. It will look up
the available resources and attach to the correct printer.
You might also need to fill in the registration info.
This worked for me when I had removed all printers and re-installed my printer.
PMMail, Galleria and CopyShop, could not print any more. After this procedure all
found the correct printer and printed correctly.
Your problem might be completely different, but if you follow this correctly
you won't be causing any harm.
"Invalid frame checksum" --- line noise or etc.
While beta testing for Dani, long before the Gamma releases, I had a "chirping"
problem with one of my 2 systems which I was using. It was a full tower system,
and I was able to eliminate the chirping by putting in a new and shorter cable (24"
vs the old 30"). So-- if you have chirping, you can reduce the PIO level as
you did, or you can also take a look at your hardware, especially the cables. This
might not work for everyone, or even all of the time, but it's a place to start.
Run Time engine.
will not be called and the Java Run Time won't be executed. Thus, no failure.
by using the APPLET tag, hence you can _also_ execute the Java Run Time engine without
So you're both right. :)
Hope this helps. It _is_ confusing, to be sure.
The first Item is the IP address. the second item is the host name. The third
item is an alias. The last item I believe needs the # sign is a comment. for example...
172.16.0.1 orion orion #main computer
172.16.0.2 nebula nebula #bedroom computer
126.96.36.199 hobbes.nmsu.edu hobbes ##where os2 files are
I have cut most of the space out. I just use the same name for the alias and
for the hostsname on my two computers The third example would make hobbes the same
as hobbes.nmsu.edu and I could ping both equally well. Check out tcpcfg.exe (i usually
type it from the command line as it takes too long to find it otherwise). This brings
up the settings. One page is hostnames. The second page of that is where you can
put shortcuts and the other machines on your network. Another cool thing described
in OS/2 Ezine that you can do is to put something like this in.
I haven't tried this yet but OS/2 Ezine list about 10 addresses where those banner
ads come from and this will cause it to lookup local host first, thus, never finding
Puting your popular sites in it will eliminate one step from your browsers work
and speed up access to that site.
It has NOT been fixed. The 'real' reason is that the Adaptec drivers grew SIGNIFICANTLY
and just will NOT fit with all
the other dd's on a diskette. Some people 'die' on diskette 1, others on 2 or 3. Depends on the individual h/w you have. We do have manual instructions to build them though, please see URL
Back when Links/2 was released, it had a problem that I wrote a quick patch for
(IIRC, if your default window settings had the top view minimized, it would cause
the game to crash after trying to start a new round). The patch doesn't have anything
to do with your problem, but during its development I learned a bit about how certain
window size and position information is saved.
What you should probably try to do is get an INI editor and edit your OS2.INI
file. In it there are several applications setup for storing Links/2 child window
size/position information. Delete all of these, and start up Links/2. Hopefully
this should cause Links/2 to revert to it's defaults for your resolution. I won't
guarantee that this will work - but it certainly can't hurt to try :)
When you start your computer the primary bootstrap code in the ROM BIOS gets
executed. The processor is in real mode with a 1Mb memory address space limit. Disk
accesses are executed via software interrupts (int 13h). A read request, for example,
requires that a request block be filled. The request block 24 bits wide and specifies
the cylinder, head and sector number to be read. There are 10 bits for the cylinder,
6 bits for the head and 8 bits for the sector so the cylinder number can range from
0 to 1023, the head from 0 to 63 and the sector from 1 to 255 (sector number 0 is
All of those numbers are, in a sense, fake. Modern disk controllers do not need
or use cylinder/head/sector specifications to access the disk. All they need is
a sector number (ranging from 0 to the end of the disk) and the controller takes
care of the rest. The controller provides a reverse CHS mapping simply to satisfy
the ancient code in the typical PC BIOS. All LBA does is to provide an alternative
reverse mapping which, in the extreme case, extends the addressability of the disk
to about 8+ gigabytes. This limit is reached when all 24 bits of the request block
are filled with ones.
The ROM BIOS cannot address a larger disk using int 13h calls and since the ROM
BIOS code is what loads your operating system it follows that your operating system
must reside within the first 8+ Gb.
Once your operating system is loaded it can use whatever method it wants to access
the disk so the entire disk can be accessible.
I believe we'll see some fixes to this entire issue soon. One option is for the
BIOS to detect intelligent disk controllers and in the presence thereof access the
disk directly rather than via the int 13h mechanism. I believe that 3rd-party add-on
software such as OnTrack disk manager works that way.
Availability dates can be found at: http://www.ibm.com/java/jdk/other/portingplans.html