etc. We would return back the right menu, icon, etc. when
you opened the drive and directory with printer drivers in it. Now,
I don't hit those breakpoints at all... This worked in 6.474 and was
broken in 6.475. I still have a 6.475 build report if you want to see
what you delta'd. We didn't change anything. Honest!
I still have 6.474 on my test machine if you want to look at it.
I'm happy to look at it with you... just come and get me.
Thanks,
Kim S.
ΓòÉΓòÉΓòÉ 2.8. *58329 Most 50MHz Phoenix BIOS do not boot. ΓòÉΓòÉΓòÉ
name 58329
reference none
abstract Most 50MHz Phoenix BIOS do not boot.
duplicate
state verify
severity 3
answer dsam
symptom vis
duplicate defects:
duplicate features: none.
notes:
<Note, action: open>
Most 50MHz Phoenix BIOS do not boot.
<Note, action: note>
This problem has also been found on Ambra machines with the latest Phoenix BIOS. These machines are not 50 MHz. Paul.
<Note, action: modify>
Screen Team Approved
<Note, action: accept>
Fixed by Russ. Real time clock save and restore needed on real/protect switch. Never hit before as we were on d1 before entering prot mode, noe we enter prot mode on in disk. Paul.
<Note, action: note>
We had 3 machines with this problem in the OEM Lab on
driver 6.494.
Pamela Marshall
982-XXXX (v$ipamm)
OEM Lab
<Note, action: note>
It is totally unlear to me as to why the OEM Lab added the above comment - this fix is in 496, so it is not surprising that it fails on 494. Paul.
<Note, action: note>
We have this problem on 2 machines on driver 6.498a in the
OEM lab.
Pamela Marshall (v$ipamm)
982-XXXX
<Note, action: note>
Correction, We did not have this problem in the OEM lab.
Pamela Marshall (v$ipamm)
982-XXXX
ΓòÉΓòÉΓòÉ 2.9. *59295 SVT: Query manager extremely slow to open ΓòÉΓòÉΓòÉ
name 59295
reference
abstract SVT: Query manager extremely slow to open
duplicate
state verify
severity 2
answer lfi
symptom other
duplicate defects:
duplicate features: none.
notes:
<Note, action: open>
A loader problem is creating a consistent loop for the Query
Manager. Therefore, the Query Manager is extremely slow.
It takes a few minutes before access to the Query. A second
attempt to open the Query Manager sometimes causes the
system to hang. This seems to be a loader problem and
Paul Devriendt is currently working on this defect. Please call
Ann-Charlotte Gruber at 2-XXXX if additional information is
required.
<Note, action: note>
Fixed in 6.486 build with performance enhancements to kernel (ldr/tk/vm) and to os2char.dll/pmwin.dll/doscall1.dll/sesmgr.dll. Paul.
ΓòÉΓòÉΓòÉ 2.10. *59304 This is a regression from GA - Notebook tabs unreadable ΓòÉΓòÉΓòÉ
name 59304
reference PJ06844
abstract This is a regression from GA - Notebook tabs unreadable
duplicate
state closed
severity 4
answer dsai
symptom vis
duplicate defects:
duplicate features: none.
notes:
<Note, action: open>
When attempting to change font size from Desktop settings, the notebook
tab text is increased in size accordingly. This makes the names on the tabs
unreadable if the characters are too large for the tab. This does not occur in GA.
To recreate the problem do the following:
1. Click right mouse button on desktop and open settings notebook.
2. Click on right arrow twice to get to page 3 of 3.
3. Click on Change Font.
4. Change font size to Times 24.
5. You will notice the notebook tab text has changed in size accordingly
and will be unreadable.
For more information contact Ajit Abhyankar at (2-XXXX) or John O'Neil (2-XXXX).
<Note, action: modify>
Screen team Approved
<Note, action: assign>
This problem is in the workplace handling of the desktop notebook
pages. The notebook page is assigning the font to the notebook tabs
instead of to the Details View display! The proper usage of the font
information needs to be done in the workplace code, not in the
graphics engine or fonts.
<Note, action: note>
While you are looking at this, it also seems that if you are changing
the font for the tree view, it changes the font for the icon view
as well.
James
ΓòÉΓòÉΓòÉ 2.11. 59344 When system is locked and alarm goes off; alarm on top of locku ΓòÉΓòÉΓòÉ
name 59344
reference
abstract When system is locked and alarm goes off; alarm on top of locku
duplicate
state working
severity 3
answer inti
symptom use
duplicate defects:
duplicate features: none.
notes:
<Note, action: open>
To recreate the problem I followed the customer's
steps one by one:
1.- Double click on the alarms icon
2.- Left click on ALARMS-SET ALARM
3.- Number = 0
4.- Status = ON
5.- Day = Every Day
6.- Hour = Every Hour
7.- Minute = 00
8.- Graphic = None
9.- Comment = Leave it blank
10. Tune = 0:Default Tune
11. Activate Every Alarm time occurrence
12. Select PopUp ** ( YOU MUST SELECT POPUP
FOR THE PROBLEM TO OCCUR
13. Left click on SET
14. From the OS/2 window set the time to be 12:59
15. Lock the workstation
16. Wait for the alarm to go off
17. Type an incorrect password ( The alarm popup
shows on top of the lockup screen ).
<Note, action: modify>
Screen team Approved
<Note, action: assign>
Change Team: Delegated work item!
<Note, action: modify>
Adding the APAR field which was missing. Modified.
<Note, action: note>
This defect is available; CT played ping-pong before APAR info existed
<Note, action: note>
Changed the lockup to replace the original Message Box that
warned of an incorrect password being typed in, instead coded a
Dialog Box. The thought was that a dialog box can 'grab' the
focus and a message box can't. However, the Alarm Window
that comes in on top of the incorrect password notification is
sysmodal. The dialog box that I coded is also sysmodal. AND
the system doesn't handle multiple sysmodal windows very well.
SO...there could be a major design change here. Am awaiting
James Taylors return from a conference next week.
ΓòÉΓòÉΓòÉ 2.12. 59480 BETA:WIN_RUNMODE description is incorrect ΓòÉΓòÉΓòÉ
name 59480
reference
abstract BETA:WIN_RUNMODE description is incorrect
duplicate
state canceled
severity 3
answer invdup
symptom use
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
BETA:Bring up the WIN-OS2 settings in the settings notebook for a windows app.
The WIN_RUNMODE parameter has changed from the GA version but the description
field has not been updated to reflect the changes.
<Note, action: return>
This is a duplicate of defect 59574 already written by Mel.
-- Ayo Anise (2-6794)
ΓòÉΓòÉΓòÉ 2.13. *59509 BETA:SYS3006 on AUTOEXEC.BAT DOS settings change ΓòÉΓòÉΓòÉ
name 59509
reference
abstract BETA:SYS3006 on AUTOEXEC.BAT DOS settings change
duplicate
state closed
severity 3
answer dsai
symptom fnwad
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
BETA:If you change the AUTOEXEC DOS setting in a DOS Full Screen session
to point to your batch file, you get SYS3006 when the session starts.
The SHELL statement in the CONFIG.SYS and the DOS_SHELL statement in the
DOS settings correctly point to the path for the command.com.
User advises this function did work in GRE-WIN earlier driver.
(John Beidl in Raleigh)
<Note, action: accept>
I've added parameter passing to the DOS_AUTOEXEC. The routine
that stepped through the parameters had a bug. It should now work.
ΓòÉΓòÉΓòÉ 2.14. 59512 BETA: User has pointed out that the tutorial still refers tduplicate ΓòÉΓòÉΓòÉ
name 59512
reference
abstract BETA: User has pointed out that the tutorial still refers tduplicate
state canceled
severity 3
answer valunr
symptom vis
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
BETA: User has pointed out that the tutorial still refers to OS/2 2.0
instead of OS/2 2.1
<Note, action: assign>
All tutorial text changes are made through ID. Roberta Carey 3-XXXX
<Note, action: accept>
We have changed the tutorial to reflect the OS/2 2.1
be
in the next beta driver.
<Note, action: return>
This defect was corrected under another defect number.
ΓòÉΓòÉΓòÉ 2.15. *59514 BETA:shutdown dialog box refers to 2.0 instead of 2.1 ΓòÉΓòÉΓòÉ
name 59514
reference
abstract BETA:shutdown dialog box refers to 2.0 instead of 2.1
duplicate
state closed
severity 3
answer inti
symptom vis
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
BETA: User has reported that the SHUTDOWN dialogue box refers to 2.0
instead of 2.1
Please transfer this to the correct component if this is the wrong one.
<Note, action: return>
I do not understand this defect. THere is no reference to os/2
versions in the shutdown dialog box or any other part of shutdown.
please explain further.
--Mindy Pollack
<Note, action: note>
12/23/92-The 2.0 I was referring is at the top of the Shutdown Dialogue when
you request to shutdown. Users reported they thought it should be 2.1
<Note, action: assign>
VAL,
The problem here is the title of the desktop (in the 20 rc file)
is called OS/2 2.0 Desktop. We agreed with usability to change
it to "Desktop". (leave OS/2 1.3 Desktop and WIN 3.1 Desktop the
way they are). Please send a note to me when you have
completed this defect so I can tell ID that it is definite.
--Mindy
<Note, action: assign>
Per Dylliam approval this MRI change is acceptable.
<Note, action: accept>
The title of the desktop has been changed from OS/2 2.0 Desktop to Desktop.
ΓòÉΓòÉΓòÉ 2.16. *59530 BETA:Running HELP in PAX/PM folder disables help ΓòÉΓòÉΓòÉ
name 59530
reference
abstract BETA:Running HELP in PAX/PM folder disables help
duplicate
state closed
severity 3
answer inti
symptom fnwad
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
BETA: User reported and I verified that with the FAX/PM folder open, if
you RMB on an icon and select help and then general, it works okay. But
if you now do the same thing to another icon in that folder, help seems
to get disabled everywhere. You click on it and nothing happens. I can
only get the error when I use the FAX/PM folder. In other folders, the
first help screen keeps getting overlayed by the latest. This folder
seems to be working differently.
Please transfer this to the correct component if I made the wrong choice.
Bob Rosenman
3-XXXX
<Note, action: assign>
Please verify resid's with Anita Soto. The Fax/PM viewer and
Fax/PM Scheduler icons should be linked to Master help index.
<Note, action: note>
I was able to recreate the problem by hitting F1 on Fax/PM viewer
icon and afterwards it seemed all the helps were disabled.
<Note, action: accept>
1/8/93 (Val Robinson)
The correct resid's were used for the Fax/PM viewer and scheduler(21500) and the correct helplibrary name (WPINDEX.HLP) was
also used to enable the help screens to work properly.
ΓòÉΓòÉΓòÉ 2.17. 59536 BETA:SYS3175 on TYPE with MORE misspelled ΓòÉΓòÉΓòÉ
name 59536
reference
abstract BETA:SYS3175 on TYPE with MORE misspelled
duplicate
state canceled
severity 3
answer invdup
symptom fnwad
duplicate defects:
duplicate features: none.
notes:
<Note, action: open>
BETA: User has reported and I can verify the following error:
Enter- type a:readme.doc | mroe (more is misppelled)
I get the correct error message that it doesn't know "mroe" command.
Reenter the command with "more" spelled correctly. You get SYS3175,
SYS1808 with exception 0005.
Run from OS/2 window.
Bob Rosenman
3-XXXX
Please transfer to correct component if this is the wrong one.
<Note, action: assign>
Assigning to proper component.
<Note, action: return>
Duplicate of 59591 in mkio component.
ΓòÉΓòÉΓòÉ 2.18. *59550 BETA: DIR /S figures the bytes used incorrectly ΓòÉΓòÉΓòÉ
name 59550
reference
abstract BETA: DIR /S figures the bytes used incorrectly
duplicate
state closed
severity 3
answer asni
symptom fnwad
duplicate defects:
duplicate features: none.
notes:
<Note, action: open>
BETA:Users have reported and I have verified that the DIR /S command is
showing a very high incorrect value for the bytes used field both in HPFS
and FAT partition and independent of the size of the partition.
Please transfer this to the correct component if I have indicated the wrong
one.
<Note, action: assign>
Assigning to proper component.
<Note, action: accept>
Correct errors in bytes used logic and print out free bytes for
each drive when a change of drives occur from multiple dir
parameters.
ΓòÉΓòÉΓòÉ 2.19. 59552 BETA: Use of HELP in FAX/PM folder disables HELP in system ΓòÉΓòÉΓòÉ
name 59552
reference
abstract BETA: Use of HELP in FAX/PM folder disables HELP in system
duplicate
state canceled
severity 3
answer
symptom fnwad
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
BETA:User reports and I have verified that if you open the FAX/PM folder
in the the productivity folder and do a RMB on any of the 3 icons and select
help and then general help, it works okay. If you then do the same thing
on another of the icons in that folder, the help function seeems to be
disabled from that point on. You can select help but see nothing.
In similar operations in other folders, the latest requested help overlays
the current one, but it doesn't seem to work in this folder.
I thought I had submitted this problem yesterday as number 59530 but now I
can't find it in the system, so I am resubmitting.
Please transfer to correct component if I've indicated the wrong one.
Bob Rosenman
3-XXXX
<Note, action: cancel>
This is a dupe of 59530. Problems in CMVC data base concerning the dev owner
of this component caused me to think 59530 was lost. After the CMVC folks
straightened things out, I saw this is a dupe so I am cancelling it.
ΓòÉΓòÉΓòÉ 2.20. 59555 BETA:Trap E copying OS/2 clipboard then pasting WINOS2 clipduplicate ΓòÉΓòÉΓòÉ
name 59555
reference
abstract BETA:Trap E copying OS/2 clipboard then pasting WINOS2 clipduplicate
state canceled
severity 3
answer valunr
symptom thipe
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
BETA:User reported following TRAP E which I have reproduced-
Bring up OS/2 window and do a COPY ALL from the system menu. Then start
WINOS2 full screen and bring up the notebook applet. Do a paste.
Trap E results.
Easy to reproduce. Contact me if you need any specific Trap info.
Please transfer to correct component if this one is incorrect.
Bob Rosenman
3-XXXX
<Note, action: assign>
This is not a WinOS2 issue but a viow issue. The dialog box
in question is in viow.
Darren & GlenP
<Note, action: cancel>
I no longer see the problem in this latest driver (6.481)
ΓòÉΓòÉΓòÉ 2.21. *59576 BETA:FAX/PM help missing for modem tuning in notebook ΓòÉΓòÉΓòÉ
name 59576
reference
abstract BETA:FAX/PM help missing for modem tuning in notebook
duplicate
state closed
severity 3
answer docm
symptom use
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
BETA: User has reported and I have confirmed that the help for the FAX/PM
Schedular applet is missing help info for the Modem Tuning page in the
notebook under Communication then Setup.
<Note, action: return>
The Setup (under Communications then Setup) option
allows you to change certain parameters which are listed
under Miscellaneous Options, and Receive Options.
Modem Tuning is not an option that you can change and therefore
is not listed on the Fax/PM Setup help panel. The Modem Tuning
help panel discussing SEVERAL OPTIONS that you CAN change. To
get help for modem tuning, follow the instructions below.
- While in the Scheduler, select communication.
- Select setup
- Select any field (ie. Scan time) by pressing mouse button one.
- Press F1
You will get the Modem Tuning Help Panel.
Thank you,
Anita Soto (2-XXXX)
<Note, action: reopen>
I've spoken with Anita and I believe we agree that the Modem Tuning help
exists, but a link to it should be added to the FAX/PM Setup help screen. This
will allow users to be able to see it when they click on the Help button
that is on the Modem Tuning page or any of the previous tab pages in Setup.
<Note, action: modify>
I have spoken with Anita and I believe that we agree that the Modem
Tuning help exists but a link to it should be added to the Fax/PM Setup
Help screen. This will allow users to see the help when they click on the
Help button that is on the modem tuning tab or on any other tab in the
Setup section.
<Note, action: accept>
59576 Working. Link to Modem Tuning is being added to the
Fax/PM Setup page. Anita Soto (2-XXXX)
<Note, action: modify>
59576 Working. Link to Modem Tuning is being added to the
Fax/PM Setup page. Anita Soto (2-XXXX)
ΓòÉΓòÉΓòÉ 2.22. 59578 BETA: SYS3175 access violation on MIGRATE of MS Bookshelf ΓòÉΓòÉΓòÉ
name 59578
reference
abstract BETA: SYS3175 access violation on MIGRATE of MS Bookshelf
duplicate
state canceled
severity 3
answer valunr
symptom thipe
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
BETA: User has reported SYS3175 access violation during migrate of MS
Bookshelf. We also see the problem migrating MS Publisher
While migrating MS bookshelf I get "SYS3175 a program in this session
encountered a problem and cannot continue.
Displaying the reg info it says"A program generated an access violation
at 00010181 MIGRATE.EXE 0001:0000181.
Viewer.exe is the file name that is being matched in the database.dat
This is the first and only match in the database. To prove this I created
a new database with just bookshelf in it (viewer.exe etc) and it still
failed. I have successfully migrated OS/2 and DOS programs but none that
are in the database. It looks like the problem only happens when there
is a match in the database. Any ideas? (I'm USING the latest OS2/ 2.1)
<Note, action: return>
This defect will be unreproducible on next version.
ΓòÉΓòÉΓòÉ 2.23. 59579 BETA:STARTUP.GRP path wrong in PROGMAN.INI ΓòÉΓòÉΓòÉ
name 59579
reference
abstract BETA:STARTUP.GRP path wrong in PROGMAN.INI
duplicate
state closed
severity 3
answer bldi
symptom fnwad
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
BETA: User reports and we have verified that when OS/2 is installed on other
than the C drive, the PROGMAN.INI file has the incorrect path for the
STARTUP.GRP file. The path points to the C drive, although the user has
installed OS/2 Beta on another drive such as D. Boot Manager was used to
run the beta from the other drive.
User was getting GROUP FILE ERROR.
ΓòÉΓòÉΓòÉ 2.24. 59582 BETA: Icons not recognized by find utility ΓòÉΓòÉΓòÉ
name 59582
reference
abstract BETA: Icons not recognized by find utility
duplicate
state canceled
severity 3
answer
symptom fnwad
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
BETA: A customer has sent me 104 icons that the find utility
will not recognize as icons unless they have been loaded
into the icon editor and then saved. GA + SP does not
ΓòÉΓòÉΓòÉ 2.25. 59583 BETA: Icons not recognized by find utility ΓòÉΓòÉΓòÉ
name 59583
reference
abstract BETA: Icons not recognized by find utility
duplicate
state canceled
severity 3
answer
symptom fnwad
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
BETA: A customer has sent me 104 icons that the find utility
will not recognize as icons unless they have been loaded
into the icon editor and then saved. GA + SP does
ΓòÉΓòÉΓòÉ 2.26. 59584 BETA: Icons not recognized by find utility ΓòÉΓòÉΓòÉ
name 59584
reference
abstract BETA: Icons not recognized by find utility
duplicate
state canceled
severity 3
answer
symptom fnwad
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
BETA: A customer has sent me 104 icons that the find utility
will not recognize as icons unless they have been loaded
into the icon editor and then saved. GA + SP does find
them correctly without having to load them into the icon
editor and save them first. The steps to reproduce this
are:
1) load icons into subdirectory called OS2ICONS
ΓòÉΓòÉΓòÉ 2.27. 59585 BETA: Icons not recognized by find utility ΓòÉΓòÉΓòÉ
name 59585
reference
abstract BETA: Icons not recognized by find utility
duplicate
state canceled
severity 3
answer
symptom fnwad
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
BETA: A customer has sent me 104 icons that the find utility
will not recognize as icons unless they have been loaded
into the icon editor and then saved. GA + SP does find
them correctly without having to load them into the icon
editor and save them first. The steps to reproduce this
are:
1) load icons into subdirectory called OS2ICONS
ΓòÉΓòÉΓòÉ 2.28. 59586 BETA: Icons not recognized by find utility ΓòÉΓòÉΓòÉ
name 59586
reference
abstract BETA: Icons not recognized by find utility
duplicate
state canceled
severity 3
answer
symptom fnwad
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
BETA: A customer has sent me 104 icons that the find utility
will not recognize as icons unless they have been loaded
into the icon editor and then saved. GA + SP does find
them correctly without having to load them into the icon
editor and save them first. The steps to reproduce this
are:
1) load icons into subdirectory called OS2ICONS
ΓòÉΓòÉΓòÉ 2.29. 59590 BETA: Find utility does not recognize icons ΓòÉΓòÉΓòÉ
name 59590
reference
abstract BETA: Find utility does not recognize icons
duplicate defect 58193
state canceled
severity 3
answer duplicate
symptom fnwad
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
BETA: A customer has sent 104 icons that the find utility
will not recognize as icons unless they have been
loaded into the icon editor and saved first. They are
recognized without needing to be loaded and saved using
GA+SP. Other icons that I have tried are found in GA+SP
as well as 6.479c. The problem seems specific to these
icons. The following are the steps to reproduce this problem
1) Create a new objuct from templates, both folder and
program object have been tried.
2) Go to general page of new object
3) select FIND
4) select LOCATE
5) select PATH and enter path to icons
6) select OK
7) select FIND
No objects are found. If one opens the Icon editor,
loads one of the icons, and saves it without changeing
anything, then the above steps will find the icon that
was saved and still refuses to recognize any that have
not been saved by the editor. Please contact me for the
icons that are causing the problem or if you have any
questions at phone# 2-XXXX.
<Note, action: return>
The cause of this problem is the same as what caused 58193, which
has been fixed and will go into the next post-beta build. We have
tested this scenario with a private fix for 58193 and it works.
Sheila 2-XXXX
ΓòÉΓòÉΓòÉ 2.30. *59591 BETA:SYS0447 and SYS1805 on DIR /P, ctl-break,type xx.xx ! duplicate ΓòÉΓòÉΓòÉ
name 59591
reference
abstract BETA:SYS0447 and SYS1805 on DIR /P, ctl-break,type xx.xx ! duplicate
state closed
severity 3
answer timm
symptom fnwad
duplicate defects:
duplicate features: none.
notes:
<Note, action: open>
BETA: Problem reported by user and reproduced by myself-Use os/2 window
Do a DIR /P for a directory that is more than one screen full of data.
When it pauses, do a ctrl-break.
Now do a type config.sys | more -
Right after the more shows up at bottom of screen, you get
SYS0447-The keyboard focus is not available
SYS1805-The process tried to write to a nonexistent pipe.
Please transfer this to correct component if I have indicated the wrong
one.
<Note, action: note>
There is an easier way to reproduce this problem. Simply hit
CTRL-BREAK at the command prompt (that's right, at the
[C:\] prompt), then try "MORE < CONFIG.SYS". The SYS0447
error will occur after one pageful of data, and the MORE
command will not work at all for the remainder of the session.
This problem occurs in both the OS/2 FullScreen and OS/2
Window.
-- Kevin J. North, LAN Lab 3-2805, KNORTH@BCRVMPC1
<Note, action: note>
Possible duplicate of 59536.
<Note, action: accept>
The problem was that the per session semaphore was set as owned by
KbdCharIn() and never cleared under the following conditions.
- Run a full screen protect mode session
- Hit <CNTRL BREAK>
- Use any program that makes keyboard API calls
<Note, action: modify>
CMVC:Fixed incorrect AFLD2 field.
<Note, action: note>
CMVC: cloned to new defect 61793.
ΓòÉΓòÉΓòÉ 2.31. 59595 BETA: Set DELDIR Statement Causes System Hang On Deletes ΓòÉΓòÉΓòÉ
name 59595
reference
abstract BETA: Set DELDIR Statement Causes System Hang On Deletes
duplicate
state canceled
severity 3
answer invdup
symptom thipe
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
With Statement "SET DELDIR = x:\DELETE, 512; active using the drive Icon
and then going to a directory and deleting multiple icons causes the
system to halt requiring the user to power off the machine to recover.
Remming out the statement in the config.sys file makes the problem go
away. "REM SET DELDIR = X:\DELETE,512;
<Note, action: return>
You must debug the problem before you submit a defect. There
is only a creation scenario in this problem.
Please check your problem against the first build after the beta,
it should be the build that will be created this week. There was
a fix for undelete that was not put into the beta, so check your
scenario against the proper build.
G. Simco
<Note, action: reopen>
Reopening per my conversation of 1/06/93 with Greg.
<Note, action: return>
This problem is a duplicate of defect 57983, which was not built
in the beta. I tested the submitters scenario on build 481 without
a problem.
G. Simco
<Note, action: cancel>
SInce this is a duplicate of a defect that wasn't fixed in the beta, and
has been confirmed by Greg as working in the next build I am going to
cancel this defect.
ΓòÉΓòÉΓòÉ 2.32. 59596 SET DELDIR Statement Causes System Hang on Deletes ΓòÉΓòÉΓòÉ
name 59596
reference
abstract SET DELDIR Statement Causes System Hang on Deletes
duplicate
state canceled
severity 3
answer
symptom thipe
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
With Statement "SET DELDIR = x:\DELETE, 512; active using the drive Icon
and then going to a directory and deleting multiple icons causes the
system to halt requiring the user to power off the machine to recover.
Remming out the statement in the config.sys file makes the problem go
away. "REM SET DELDIR = X:\DELETE,512;
ΓòÉΓòÉΓòÉ 2.33. *59597 BETA: DOS_INT28_FILTER missing from the DOS SETTINGS list ΓòÉΓòÉΓòÉ
name 59597
reference
abstract BETA: DOS_INT28_FILTER missing from the DOS SETTINGS list
duplicate
state closed
severity 3
answer doci
symptom fnwad
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
The online help for the "DOS_settings..." mentions that DOS_INT28_FILTER
is a changeable setting. However, this setting is not shown in the
list.
The steps to get the paragraph where the DOS_INT28_FILTER setting
is mentioned are:
- Open the settings for any DOS session
- Select the "Session" tab and press the DOS_settings... pushbutton
- Select HELP
- From the Related Information area, select "DOS AND WIN-OS/2
settings, descriptions"
- Select "Other DOS Settings"
<Note, action: assign>
I don't know what the INT28 filter setting is supposed to be.
I can tell you it is not registered by any of the standard devices
on our system as of today. You might ask Jeff Muir about this.
I am re-routing this to BASEINFO because that component owns
the file MRI\HELP\DOSPRMN, where the text in question is located.
ΓòÉΓòÉΓòÉ 2.111. 60040 BETA: Can not Boot DOS, if OS/2 Creates Partition over 1024duplicate ΓòÉΓòÉΓòÉ
name 60040
reference
abstract BETA: Can not Boot DOS, if OS/2 Creates Partition over 1024duplicate
state tcanceled
severity 2
answer invwad
symptom use
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
I installed OS/2 2.1 beta. Having two 80M MFM drives, I was excited about
support of over 1024 cylinders, since my second drive has 1314 cylinders.
Therefore, I created a second partition, made of cyls over 1024, 18Meg,
using FDISKPM. Worked great. For the first time, OS/2 can manage more
than 10 year old limit of 1024 cylinders! The new IBM1s506.ADD does that.
Slight problem, however.
Once OS/2 partition over 1024 is created, DOS no longer boots. Not only
from any hard drive, but any DOS! Even MS DOS 5.0 from a diskette. It
does not like that OS/2 partition, whether FAT or HPFS, over 1024 cyls.
Upon boot, the drive light comes on and stays on, that's it.
Once that partition is deleted, DOS boots.
Since OS/2 does not support programs using VCPI (In my case all important
ORACLE database), capability of booting DOS is absolutely necessary.
In comparison, DOS works fine when that partition is created by Ontrack
disk manager, and accesses that partition via DMDRVR.BIN driver, the
facto statndard, that comes with DOS 5.0. Apparently OS/2 does not
seem to adhere to that convention.
A question to IBM:
Considering that OS/2 is a better DOS than DOS, the above incompatibility
is:
- A temporary bug that will be eventually corrected to be in sync with
DOS & Ontrack.
- It is not a bug, it works as planned, in this case, OS/2 documentation
should be updated with a new restriction, that if you create a part-
ition over 1024 cylinders, using FDISKPM, you will no longer be able
to boot DOS, even from a DOS installation disk.
I hope the answer is the first one.
Beta tester
If you have any questions, please contact Sheila McDOnald-Rich on 3-XXXX.
<Note, action: assign>
Rerouting to FDISK component.
<Note, action: return>
This is working as designed. The restriction of booting from
greater than 1024 cylinders is neither an OS/2 or DOS limit-
ation but a CBIOS hardware limit. The int 13 cylinder field
is rerstricted to 10 bits, 1023 value. Int 13 is required for
booting up until the machine is switched to protect mode.
Besides booting, when real DOS is running if a program
issued an int 13 it would fail. To circumvent around this
I would suggest that you repartition the drive, using OS/2
FDISK and make a partition that doesn't exceed the 1023
limit, and then make a logical partition out of the rest. The
less than 1023 partition will be fat and can be booted and
accessed by everyone. The partition exceeding the 1023
limit will be hpfs and will be supported by OS/2, includuing
the dos box. You may want to run Boot Manager or dualboot
to facilliate this. Also some machines will may map this same
drive geometry so as utilize the entire drive space without
exceeding the 1023 limit.
<Note, action: cancel>
WAD
ΓòÉΓòÉΓòÉ 2.112. 60041 BETA: Comm Errors ΓòÉΓòÉΓòÉ
name 60041
reference
abstract BETA: Comm Errors
duplicate
state canceled
severity 3
answer invinf
symptom use
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
I am running PMFax 1.16, however the status box gets covered up and I forget
to turn receive off. It's just a nuiscance when I do forget.
A beta Tester
If you have any questions, please contact Sheila McDonald-Rich on 3-XXXX.
<Note, action: cancel>
Forwarded Suggestion to Planning
ΓòÉΓòÉΓòÉ 2.113. *60046 BETA: PMSEEK does not retain defualt editor ΓòÉΓòÉΓòÉ
name 60046
reference
abstract BETA: PMSEEK does not retain defualt editor
duplicate
state closed
severity 3
answer chkm
symptom fnwad
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
BETA: When using PMSEEK if one selects an editor other than
E.EXE as the editor filespec, select options, select
Set defaults, close PMSEEK and reopen it. It again
defaults to E.EXE as the editor filespec. This is also
the way it functions in GA.
ΓòÉΓòÉΓòÉ 2.114. *60047 REGR: Icon positions not restored in folders, icons lost. ΓòÉΓòÉΓòÉ
name 60047
reference
abstract REGR: Icon positions not restored in folders, icons lost.
duplicate
state verify
severity 3
answer dsai
symptom vis
duplicate defects:
duplicate features: none.
notes:
<Note, action: open>
Icon positions are not restored when a folder is closed then opened.
Also, icons are lost on subsequent opens. (i.e. Open OS/2 system
folder and then move an icon, close the folder and reopen, do this
several times with several folders and you will see icon misbehavior).
Sometimes the system will appear to hang, due to a loop in
VacateFolderThread.
I've talked to Peter Magid about this.
-Sheila 2-XXXX
<Note, action: accept>
Left off the check to increment the container record
- Peter G. Magid, 2-XXXX
<Note, action: modify>
Crit: Frito Lay; (S. Wuest)
ΓòÉΓòÉΓòÉ 2.115. 60052 BETA: Include page of desktop settings has no page nums ΓòÉΓòÉΓòÉ
name 60052
reference
abstract BETA: Include page of desktop settings has no page nums
duplicate
state canceled
severity 4
answer intit
symptom vis
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
The desktop settings tab "INCLUDE" does not have any page numbers.
The "page X of X" part of some tabs does not show entire last number.
<Note, action: return>
This has been this way since GA. We already have another
TRSed defect for the same problem.
James Taylor 982-XXXX
<Note, action: modify>
This will never get fixed unless we submit to it. I have also found a problem in
many of the object settings. System settings, Screen TAB has Page 1 of 2 on it and
if try to go to page two, you go to the next TAB!. I could give you many such occurances
free for the asking....resubmit!
<Note, action: reopen>
This is a valid defect which make users think there is a page 2 when there is not one.
It is confusing and troublesome...It NEEDS to be fixed.
<Note, action: return>
Steve, I am TRS'ing defect also. We will have this fixed
in the next release. Claudette 2-XXXX
<Note, action: cancel>
Cancel due to priority. Needs to be to be added for next release
<SHR>
ΓòÉΓòÉΓòÉ 2.116. 60053 BETA: Icons in startup don't unhash ΓòÉΓòÉΓòÉ
name 60053
reference
abstract BETA: Icons in startup don't unhash
duplicate defect 59807
state canceled
severity 3
answer duplicate
symptom vis
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
BETA: If one puts a program icon, say a Dos window with
starting from a diskette image, into the startup folder,
shut down and reboot, the program is started. If one
then closes the window from the task list, the icon
remains hashed although the program is closed and
no longer appears in the task list.
<Note, action: return>
this is a duplicate and will be fixed in next borg build
<Note, action: cancel>
duplicate 59807
ΓòÉΓòÉΓòÉ 2.117. 60062 BETA: EDIT.HLP file needed for QBASIC /EDIT not in \OS2\MDOduplicate ΓòÉΓòÉΓòÉ
name 60062
reference
abstract BETA: EDIT.HLP file needed for QBASIC /EDIT not in \OS2\MDOduplicate
state canceled
severity 3
answer docmp
symptom fnwad
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
Using a DOS session, open QBASIC with /EDIT param, get message "File EDIT.HLP not found, Please
insert diskette in drive or change options+help path". If you hit enter it does nothing, you MUST cancel
to continue using the editor.
<Note, action: assign>
I spoke to A.Ford, this is not a sys.editor problem. She suggested
that I re route this to DOS Emulation DOS5 or WIN/OS-2.
<Note, action: assign>
It is not clear to me whether the .hlp file even exists on the
harddisk. In either case I do not own QBasic.
<Note, action: return>
The OS/2 BORG Project Office, 1st/2nd line development mgrs
want this defect cancelled. We do not ship the help according
to the Product Plan. Please accept/cancel this defect on
your end as I cannot do a cancel and this is what I have been
asked to do by the people in charge of OS/2. K.Hamill,
Project Office.
<Note, action: cancel>
Canceled Per khamill <SHR>
ΓòÉΓòÉΓòÉ 2.118. *60063 BETA: File IBM2M57.ADD placed in \OS2 on NON-IBM machines ΓòÉΓòÉΓòÉ
name 60063
reference
abstract BETA: File IBM2M57.ADD placed in \OS2 on NON-IBM machines
duplicate
state closed
severity 2
answer bldm
symptom fnwad
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
The file IBM2M57.ADD for the multimedia machines is being placed in the \OS2
subdirectory by the installation even on NON-IBM machine types.
<Note, action: assign>
assign to ins from inst
<Note, action: note>
Deleted IBM1M57.ADD at the end of install.
<Note, action: modify>
Reopen due to reproduced error in 6.488 on 486-33 Micronics Mthrbrd.
<Note, action: modify>
CMVC:Fixed incorrect AFLD2 field.
<Note, action: note>
CMVC: cloned to new defect 61022.
ΓòÉΓòÉΓòÉ 2.119. 60069 BETA: Minimized OS/2 programs vanish if in startup folder ΓòÉΓòÉΓòÉ
name 60069
reference
abstract BETA: Minimized OS/2 programs vanish if in startup folder
duplicate
state canceled
severity 3
answer invdup
symptom vis
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
Programs in startup folder that should start minimize at IPL do not.
Created shadow's of EPM.EXE and PULSE.EXE and placed in
startup folder. Enabled settings for both programs to minimize
to the desktop. Started both programs and minimized to the
desktop. OK so far. Shutdown machine and pressed CTRL-ALT -DEL.
When system came back up the MINIMIZED pulse and epm were
nowhere to be found on the desktop. Hit CTRL-ESC to bring up
task list. They were both listed as running. Looked into the
minimized window viewer and VOILA they were in there!
Contact Marc Schneiderman 3-XXXX for more information.
<Note, action: return>
this is a dup of 59993. please look through our database before
opening defects.
<Note, action: modify>
sev one is for build breaks and sev 2 is for test case blocks
ΓòÉΓòÉΓòÉ 2.120. 60079 BETA: Deadlock using LAN Network Mgr ΓòÉΓòÉΓòÉ
name 60079
reference
abstract BETA: Deadlock using LAN Network Mgr
duplicate
state canceled
severity 3
answer invinf
symptom comp
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
(I'm not certain I've got the right component, but...)
Reported by several users on OS2BETA CFORUM and over the hotlines:
The 2.1 beta deadlocks when the icon for LAN Network Manager is
selected. The steps are pretty simple - at boot time the LAN
requester (2.0) and Comm Manager both come up okay. The user
then selects the LNM icon and the system deadlocks. The mouse
moves, but the nothing responds to it. Keyboard is also dead,
and power-off is required.
I called the LAN Network Mgr folks in Raleigh, but nobody could
tell me whether anyone there had tested it under 2.1.
Another note - customer encountered the "deadlock" late in the
evening and just went home, leaving the system running. In the
morning the clock was running, sort of, but only activating
every three or four minutes (minute hand would jump from 8:20 to
8:24 to 8:27 etc), and his pulse screen was up but the red line
had disappeared halfway across it. FWIW....
Dan Lee 2-XXXX
<Note, action: return>
I don't understand what the user was starting. What is the
lan manager icon? what does it look like and what is the
exact text? I'm trying to figure out if this is a lan aware shell
problem or a lan manager problem.
--Mindy
<Note, action: reopen>
It could be either of the above. IBM's LAN Network Manager is a product
out of Raleigh. It should not be confused with IBM's LAN Services or
with Microsoft's LAN Mgr. It is in version 1.1 now, but customers have
been reporting 2.1 deadlocks using versions 1.0 and 1.1 of the IBM Network
Manager. When installed, it puts an icon on the desktop. It worked fine
under 2.0, but under the 2.1 beta it deadlocks.
Dan Lee
<Note, action: assign>
this problem should be looked at by the lan network manager
folks in Raleigh.
Mindy Pollack
<Note, action: assign>
This program worked on 2.0 GA now it does not work on Borg. I find
it hard to believe the problem is the program.
<Note, action: return>
I am returning this insufficient infomation per my conversation with Paul Cheatham
<Note, action: cancel>
Fix/Work-around documented in 61554.
<Note, action: note>
This was nothing at all to do with 61554. This was a kernel problem that has been fixed. Paul.
ΓòÉΓòÉΓòÉ 2.121. 60080 Hangs on diskette 1 on Compudyne 486 Notebook ΓòÉΓòÉΓòÉ
name 60080
reference
abstract Hangs on diskette 1 on Compudyne 486 Notebook
duplicate defect 58329
state canceled
severity 3
answer duplicate
symptom thipe
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
User has installed Borg on other systems successfully, but on the Compudyne 486DX, the install hangs when diskette 1 is called for. The Compudyne has been running the GA level and the 11/29 level of OS/2 without problems.
<Note, action: return>
duplicate of 60017
ΓòÉΓòÉΓòÉ 2.122. 60081 BETA: Backup program in 2.1 does not work correctly ΓòÉΓòÉΓòÉ
name 60081
reference
abstract BETA: Backup program in 2.1 does not work correctly
duplicate
state canceled
severity 3
answer invwad
symptom fnwad
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
Backup program provided in Welcome folder correctly backs up
everything - Backup program in 2.1 beta does not.
Preload backup : 29712 bytes 10/26/92
2.1 backup : 84069 bytes 12/09/92
<Note, action: modify>
IN the 2.1 backup issued BACKUP C:\*.* A: /S
did not list or appear to back up system files: OS2BOOT,OS2KRNL
OS2LDR WP ROOT. SF / Creating Backup and Restore programs
from the Welcome Folder and executing BOOTDISK.EXE. This program
allowed backing up the entire system, including the OS2KRNL,
allowed formatting of the hard disk prior to restore and allowed
<Note, action: modify>
a complete restore of the system.
<Note, action: return>
BACKUP was designed to back up only user files. In order to have BACKUP to provide the same functionality as PRELOAD BACKUP a new feature would have to be introduced.
abstract BETA: Seamless app causes PM debugger to vanish mysteriouslduplicate
state working
severity 3
answer chki
symptom vis
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
When using the C/Set 2 presentation manager debugger with
Codewright running as a seamless app the debugger mysteriously
vanishes. The C/Set 2 PM debugger is CSD #30 (Dec. 92). It
works flawlessly with multiple open OS/2 apps, and an open OS/2
window for compiling and linking. The specific app that was being
debugged when this behavior occured was the hello program from
the toolkit.
<Note, action: assign>
OS/2 Level 3.0 Change Team is working on this, contact Joe Wieloch 3-XXXX
<Note, action: return>
The PM Debugger IPMD.EXE posts a destroy window to the
debugger source window causing the source window to be
destroyed. Since the application is destroying the window,
this is an application error and should be assigned to the
PM Debugger development team. They should be able to provide
insight into why the application is posting a destroy message.
-- OS2 Change Team (Joe Wieloch 8-982-6261 / 3-6261)
<Note, action: modify>
Screen Team Approved
<Note, action: note>
Roger Early (8-545-XXXX), a PM Debugger developer, called me
today. The debugger is doing a DosDebug call and receiving an
invalid notification code (303) in the debug buffer. He said that
this was identified in the beta of PM Debugger 2.0 and that
Arthur Roberts has created a fix. I talked to Arthur who delta'd
code against defect 61066 to fix this problem, the fix will be in
the Borg 6.492 build. PM Debugger ver 1.0 with the CSD will
need to be tested on the 6.492 build.
-- OS2 Change Team (Joe Wieloch 3-6261)
<Note, action: reopen>
Problem of running C/Set2 PM debugger along with a seamless
windows app still persists in the 6.492 driver. In addition
the Borland C++ Turbo Debugger for OS/2 also crashes when
tracing thru an app that makes a call to create a new window.
<Note, action: note>
The test scenerio originally included the PM debugger of C/Set2
but after more extensive testing it seems that the beta version
of Borland's C++ Turbo Debugger also exhibits abnormal behavior
when stepping thru a sample program which is making a call
to create a window. This behavior only manifests itself while
a seamless app is running in the backround.
<Note, action: note>
The Borland PM Turbo Debugger exhibits abnormal behavior
when stepping thru source code that creates a window when
a seamless app is in the backround. Rich Wesson of Borland
International was contacted 2-9-93 and made aware of this
situation. His number is 408-438-XXXX ext 606.
<Note, action: note>
Spoke to James Boch, QA Mgr for the Borland Turbo
debugger product. He said they were targeting OS/2 2.0 for their
upcomming release, and were not actively testing under the 2.1
BETA. He indicated Borland's priorities did not include
addressing this issue to resolution at the present time.
Joe Wieloch spoke to Arthur Roberts, who is responsible for
DosDebug. Arthur explained DosDebug calls only reflect the
state of the system. It is up
Lexington, KY and Borland Int'l to handle special cases.
Currently the IBM PM debugger developers are working on
a new release and are aware of the problem with running
seamless apps concurently on the OS/2 desktop.
<Note, action: return>
Per information stated by Marc Schneiderman. Please note the
following phone numbers:
PM Debbuger: Patrick Gerstle 8-545-XXXX
Roger Early 8-545-XXXX
OS2 DosDebug: Arthur Roberts 8-982-XXXX
OS2 Chng Team: Marc Schneiderman 8-982-XXXX
Joe Wieloch 8-982-XXXX
<Note, action: reopen>
Spoke to Roger Early who felt the problem with the C/Set 2
debugger, when running a seamless app, was not application
related. Since the same problem exists in the Borland C++
Turbo Debugger at exactly the same point, when tracing through
a call to WinCreateStdWindow I am reopening this defect.
<Note, action: note>
Both the IBM PM debugger and Borland Turbo debugger step
through calls to WinCreateStdWindow fine under 2.0 and
Service Pak.
<Note, action: assign>
DosDebug is notifying the PM Debugger that system resources are
unavailable. To determine the real problem, it is necessary to get
more information about what calls are made to DosDebug and
what DosDebug is checking/returning. Marc S. also tested on the
4.96 build with a 1/20/93 version of IPMD.EXE, in this case the
system locked up, another indication that the problem might not
be in winos2. -- Joe Wieloch 3-6261 OS2 Change Team .
<Note, action: return>
This is not an error condition. Rodger Early in lexington can explain
what changed in his debugger to cause this to appear. The system
resource which is being held is a semiphore two people can not control
the same system resource at the same time. If you are in PM or any
other area which requires screen changes or updates this is a possible
message. If you need all of the details ask Rodger for the Apar number.
<Note, action: reopen>
Please route directly to Glen Puchtel. He has worked on
debugging this problem with Dave Medina and has a fix.
<Note, action: accept>
It seems that we (PM) are holding the user semaphore (fsrsUSER)
at the time we need to do a DosLoadModule on pmviop.dll. This
causes problems for debuggers so a method needs to be identified
to load the module without having the user semaphore. So far
the only safe place to do this is when the thread creates its
message queue (ie WinCreateMessageQueue), at this time we
will load "pmviop". This will change the timing somewhat,
hopefully this timing change will not cause any regressions.
ΓòÉΓòÉΓòÉ 2.176. 60611 BETA: Sound from MVDM not shut off after task switch from pduplicate ΓòÉΓòÉΓòÉ
name 60611
reference
abstract BETA: Sound from MVDM not shut off after task switch from pduplicate
state canceled
severity 3
answer invwad
symptom fnwad
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
Running SB, M-Audio.. ALT-ESC to change session to desktop still has
music from app playing in background. This is a major bug and needs
to be delt with ASAP. Known since GA 2.0. <SHR>
<Note, action: modify>
Changed phase found to be " beta ". <SHR>
<Note, action: return>
OS/2 has no way of knowing what the sound card is doing, which is the one driving the speakers. The DOS app, in the other hand, is the one driving the sound card.
<Note, action: cancel>
There must be a way to have OS/2 sense the port activity and shut it down
if the data is deemed to be of an address which was used by a killed process.
I think this is a major for many customers, I for one. Cancel due
to future enhancement projects. <SHR>
ΓòÉΓòÉΓòÉ 2.177. 60621 BETA:SETUP.TXT file needs to be removed from WinOS2 ΓòÉΓòÉΓòÉ
name 60621
reference
abstract BETA:SETUP.TXT file needs to be removed from WinOS2
duplicate defect 60649
state canceled
severity 3
answer duplicate
symptom vis
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
The text file SETUP.TXT is in WinOS2 on the 6.486 build. I talked to Ayo
Anise and he said that this file needs to be removed from the WINOS2
layout. This defect is being opened at Ayo's request.
<Note, action: return>
I have fixed this under defect #60649. Don Wakley 2-XXXX.
If you VIEW an .INF file, CMDREF.INF for instance, and "minimize" a few of
your viewed pages (say, the table of contents), you can move those icons all
over the VIEW window. If you drag the icon over the left, right, or top
edges of the VIEW window, it pops back "reasonably" and the text is
completely visible. However, if you drag it to the extreme bottom of the
VIEW window, the icon pops back and overlays the text accompanying the icon.
Also... if you have an icon or two in the VIEW window, then resize the
window in such a way as to "loose" some of the icons, I cannot see a
way to make them all appear short of maximizing the window. If you shrink
the size of that window vertically, icons get pushed off the bottom of the
window.
A Beta Tester
If you have any questions, please contact Sheila McDonald-Rich on
3-XXXX.
<Note, action: return>
The problems you describe are all due to the MDI design of the
help window. This is correct behavior for an MDI application.
We recognize that the MDI model has problems and we intend to
address these in some future release by eliminating the MDI model
but currently, this is "working as designed".
<Note, action: cancel>
WAD-to be addressed in a future release
ΓòÉΓòÉΓòÉ 2.190. 60707 BETA: Cannot create boot floppies if using 4DOS ΓòÉΓòÉΓòÉ
name 60707
reference
abstract BETA: Cannot create boot floppies if using 4DOS
duplicate
state canceled
severity 4
answer invnos
symptom fnwad
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
Part of the CD/ROM installation process is creating the boot floppies.
If the program 4DOS is used instead of COMMAND.COM, the step that
creates these diskettes will fail. The failure occurs at the point where
you are asked to insert the blank diskette and press any key to continue.
When you press the key, an error message immediately appears that
says "Possible error creating the OS/2 2.1 installation diskette".
The program 4DOS is marketed by JP Software. I contacted them and
they investigated and believe the problem is in the MKINDSKF.EXE
routine. They can be reached at 617-646-XXXX The contact's name is
Tom Rawson.
<Note, action: return>
the program that creates diskettes from the borg CD was not developed by the Install group. This was a special program only for the borg beta. It will not be part of the shipped product. It was produced by a team led by Eva Cannova, pls contact her.
ΓòÉΓòÉΓòÉ 2.191. 60709 BETA: Model 70 dies on boot ΓòÉΓòÉΓòÉ
name 60709
reference
abstract BETA: Model 70 dies on boot
duplicate
state canceled
severity 3
answer invinf
symptom vis
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
Customer has Model 70 with scsi quantum Drivekit 245 as well
as ESDI controller. Installed using diskettes with sysinst2.exe
dated 12-26-92. The system hangs after booting to OS/2 logo
is displayed. Steve Best has copy of exact error message.
<Note, action: note>
When the system boots, immediately after the OS/2 logo is
displayed, the customer gets the following message:
The system detected an internal processing error
at location ##0160:fffba480 - 000d:00063480
1157, 7019
0386000d1
<Note, action: return>
Please ask the customer for registers when this traps occurs.
With the information available it can not be determined where in
the kernel this trap is occurring.
Steve Best
3-XXXX
<Note, action: assign>
The trap occurred in file vdmm.c (7019) on line 1157. The code
was testing for a bad return code (most likely 8) from VMAllocKHB.
We should not IPE for an out of memory condition.
<Note, action: assign>
The trap occurred in file vdmm.c (7019) on line 1157. The code
was getting a bad return code (most likely 8) from VMAllocKHB.
If the rc was 8, we should not IPE, since its only an out of memory
condition.
ΓòÉΓòÉΓòÉ 2.192. *60710 Beta : INT_DURING_IO setting hangs system ΓòÉΓòÉΓòÉ
name 60710
reference
abstract Beta : INT_DURING_IO setting hangs system
duplicate
state closed
severity 3
answer dsai
symptom thipe
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
BETA: When the INT_DURING_IO setting is used for uninterupted
sound with multimedia applications the system hangs.
<Note, action: accept>
VPIC's semaphore was being posted at terminate time. The slave thread
thought it had a valid request. Most likely, parts of memory were destroyed
based on this bogus request. VPIC now validates the request before attempting.
If the correct flag is not set, it exits the routine.
ΓòÉΓòÉΓòÉ 2.193. *60724 BETA: A Leading Space on Lock Pass Word Causes Problem ΓòÉΓòÉΓòÉ
name 60724
reference
abstract BETA: A Leading Space on Lock Pass Word Causes Problem
duplicate
state closed
severity 3
answer inti
symptom fnwad
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
I have tested the following and can reproduce the problem on the
6.486 build. Mike Jasinski
Subject: Lockup Problem
It appears a password which begins with a space screws up the help
function on the locked screen. Given such a password, if the system
is locked and if help is then selected and cancelled, there is
no way to have the password accepted. Entry of the first space will
return the help window. Only way out is to reboot, and that doesn't
have very nice results since there was no orderly shutdown.
<Note, action: assign>
do not write any defects against wpsl please.
ΓòÉΓòÉΓòÉ 2.194. 60741 BETA: Install confuses D & C drives. ΓòÉΓòÉΓòÉ
name 60741
reference
abstract BETA: Install confuses D & C drives.
duplicate
state canceled
severity 3
answer invinf
symptom appf
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
CorelDraw: Trying to install ADOBE type manager on D drive - install assumes
it is on C drive. Problem on 2.1 Beta - CorelDraw for OS/2 & Windows.
<Note, action: return>
The defect does not have enough useful information to debug the
problem. The submitter needs to add more information in order
to debug this problem.
<Note, action: modify>
Screen Team Approved
<Note, action: return>
I have CorelDraw 3.0 for Windows, and ATM Adobe doesn't come
with it.
If you are using OS/2 2.1, and installed the OS/2 operating system on
default driver (which is C:), it automatically creates a
C:\PSFONTS directory. And the Winos2 ATM version 2.5 default
is set to C: also. All this information is kept under winos2\ATM.INI.
Now the question unclear in the problem is if you already
installed ATM Adobe and it resides on drive D:, and you install
the operating system on driver C:, then the ATM is still default
to C: as described in the previous paragraph. This is working
as design. There is no entry during OS/2 2.1 installation that asks
the user whether he has ATM adobe fonts installed or not. The
only thing the user can do is to start ATM, and run ADD option.
Now if you installed OS/2 2.1 Beta on the default driver D:, then
\PSFONTS will be created on D:.
Joe Luu
ΓòÉΓòÉΓòÉ 2.195. 60744 BETA:Install hangs on diskette 1 on AMBRA machine ΓòÉΓòÉΓòÉ
name 60744
reference
abstract BETA:Install hangs on diskette 1 on AMBRA machine
duplicate defect 58329
state canceled
severity 3
answer duplicate
symptom thipe
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
BETA:Several users have reported the Install process hangs on Diskette 1
on an AMBRA machine. Craig Bennett thinks we didn't see problem here
because our machines are downlevel. Paul Devriendt is also aware of problem.
<Note, action: return>
This problem has now been reproduced in the OEM Lab in Boca, and is the same as defect 58329. Paul.
ΓòÉΓòÉΓòÉ 2.196. *60746 BETA: starting windows app from startup.cmd corrupts desktoduplicate ΓòÉΓòÉΓòÉ
name 60746
reference
abstract BETA: starting windows app from startup.cmd corrupts desktoduplicate
state closed
severity 3
answer asnm
symptom vis
duplicate defects:
duplicate features: none.
notes:
<Note, action: open>
Starting a windows app from startup.cmd corrupts the full screen
Win/OS2 session. If the app was migrated then the OS/2 desktop
is corrupted. This was tested on an IBM Valuepoint with Trident
SVGA drivers in the performance test lab.
<Note, action: modify>
this defect should not be a sev. 1. Sev. 1 is for build breaks,
sev 2 is for system test case blocks and sev 3 is for needs to
be fixed in BORG
<Note, action: assign>
if the problem exists when you start the app via the startup.cmd,
then this isn't a shell problem.
--Mindy Pollack
2-XXXX
<Note, action: assign>
OS2 Level Change Team currently working on this problem, contact
<Note, action: note>
OS/2 Level 3.0 Change Team is working on this, contact Joe Wieloch 3-XXXX.
<Note, action: assign>
This problem also occurs when you try to start any WINOS2 app from
the OS2 Window command prompt (i. e. start c:\os2\mdos\winos2\clock.exe).
<Note, action: assign>
Investigating.
<Note, action: assign>
On Trident, when starting WINOS2 minimized with VIDEO_SWITCH_NOTIFICATION
set to OFF, winos2 comes up corrupted. This is not observed on other adapters.
If VIDEO_SWITCH_NOTIFICATION is set to ON, an additional BIOS
mode set is issued when VDM comes into foreground, so that the
corruption is taken care off by the winos2 driver itself.
When starting a WINOS2 app in the background (using start) and when
going into the foreground, winos2 is corrupted and there is no additional
mode set to take care of the corruption (in other words, it behaves as VIDEO_
SWITCH_NOTIFICATION set to OFF). Settings of that app's icon or WINOS2 settings
have no impact on this behaviour.
Desktop corruption on a very first switch from the WINOS2 FS
to the desktop happens only if the app was started from an OS/2 FS and
a switch to the desktop occured before the WINOS2 session was brought
full screen.
The desktop dirty flag flVVD is set by the VVID in the background
when first BIOS mode set happened, but because we switched to the
desktop first, the flag was reset. If the subsequent BIOS mode set existed,
when the vdm session went full screen, the flag would have been set again.
This is possibly a design flow in the usage of the flag on part of both
desktop and vvid.
Conclusion: If when starting WINOS2 minimized without the swith
notification set can not be fixed by VVID, this defect is out
of our realm. Will investigate why is that corruption happening in the
first place. I will also investigate why is the flag reset on a swith from
a non VDM session to the desktop.
<Note, action: assign>
On Trident, when starting WINOS2 minimized with VIDEO_SWITCH_NOTIFICATION
set to OFF, winos2 comes up corrupted. This is not observed on other adapters.
If VIDEO_SWITCH_NOTIFICATION is set to ON, an additional BIOS
mode set is issued when VDM comes into foreground, so that the
corruption is taken care off by the winos2 driver itself.
When starting a WINOS2 app in the background (using start) and when
going into the foreground, winos2 is corrupted and there is no additional
mode set to take care of the corruption (in other words, it behaves as VIDEO_
SWITCH_NOTIFICATION set to OFF). Settings of that app's icon or WINOS2 settings
have no impact on this behaviour.
Desktop corruption on a very first switch from the WINOS2 FS
to the desktop happens only if the app was started from an OS/2 FS and
a switch to the desktop occured before the WINOS2 session was brought
full screen.
The desktop dirty flag flVVD is set by the VVID in the background
when first BIOS mode set happened, but because we switched to the
desktop first, the flag was reset. If the subsequent BIOS mode set existed,
when the vdm session went full screen, the flag would have been set again.
This is possibly a design flow in the usage of the flag on part of both
desktop and vvid.
Conclusion: If when starting WINOS2 minimized without the swith
notification set can not be fixed by VVID, this defect is out
of our realm. Will investigate why is that corruption happening in the
first place. I will also investigate why is the flag reset on a swith from
a non VDM session to the desktop.
<Note, action: modify>
Screen Team Approved
<Note, action: accept>
Freeze enhanced mode session after a mode set in the bgnd.
ΓòÉΓòÉΓòÉ 2.197. 60754 BETA: performance problem - excessive time on DLL loads. ΓòÉΓòÉΓòÉ
name 60754
reference
abstract BETA: performance problem - excessive time on DLL loads.
duplicate defect 59295
state canceled
severity 3
answer duplicate
symptom prf
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
This defect was written to insure that a private fix to 2.1 BETA sent to
SAS Institute to improve 2.1 BETA run times on DLL loads is included in
the next release.
<Note, action: return>
I am at a loss to understand why you wrote this defect. As you know, this was a known problem, that was already fixed before you found the problem. Please check the database for writing defects for known problems. Thank you. Paul.
<Note, action: modify>
Screen Team Approved
<Note, action: cancel>
THe problem has been resolved
ΓòÉΓòÉΓòÉ 2.198. 60760 BETA: Driver for IBM Proprinter ΓòÉΓòÉΓòÉ
name 60760
reference
abstract BETA: Driver for IBM Proprinter
duplicate
state canceled
severity 4
answer valunr
symptom use
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
The entry for "4201 ProPrinter" appears "out of order" in the
PRDESC.LIST. It follows the II and III entries.
A Beta Tester
If you have any questions, please contact Sheila McDonald-Rich on
3-XXXX.
<Note, action: assign>
Rerouted to install.
<Note, action: modify>
Screen Team Approved
<Note, action: return>
This has been fixed for the 6.494 build. The list will be sorted
correctly in that build. Proprinter will come before Proprinter II,
which will come before Proprinter III, etc. I changed the build
tool so that the colon is not considered as one of the characters
to sort in the sort algorithm...
ΓòÉΓòÉΓòÉ 2.199. 60761 BETA: Errors in PRDESC.LIST ΓòÉΓòÉΓòÉ
name 60761
reference
abstract BETA: Errors in PRDESC.LIST
duplicate
state canceled
severity 4
answer invwad
symptom use
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
In the list of printers, PRDESC.LST, there are two entries for the 4019 and
four entries for the 4029 that are in error. The entries that call for
"LASERJET.DRV" refer to "Laserprinter" (in two places for each entry) instead
of "LaserPrinter." Note the bicapitalization? "LaserPrinter" is not a
trademark (according to the manuals that come with one) but whatever rights
IBM might have to the term would be best protected by correcting those entries.
Besides, all the other references use "LaserPrinter."
FWIW, "LaserJet" is a trademark of HP. BiCapitalization -- the industry ran
out of acronyms, or acronyms went out of style, so now two common
words get pressed together. OfficeVision, MultiMedia, BookMaster (and
BookMaster/2!);
A Beta Tester
If you have any questions, please contact Sheila McDonald-Rich on
3-XXXX.
<Note, action: assign>
Rerouted to install.
<Note, action: assign>
Rerouting from INS to LaserJet. Devnames takes the name
from the LaserJet driver itself (retruned from DevQueryDeviceNames).
I don't imagine you can change the name now, because we already
shipped with it and there would be problems on the network (drivers
on the server having one name and drivers on the requestor having
another name)...
I'll let you and Mark decide this one...
Thanks,
Kim
<Note, action: assign>
Rerouting from INS to LaserJet. Devnames takes the name
from the LaserJet driver itself (retruned from DevQueryDeviceNames).
I don't imagine you can change the name now, because we already
shipped with it and there would be problems on the network (drivers
on the server having one name and drivers on the requestor having
another name)...
I'll let you and Mark decide this one...
Thanks,
Kim
<Note, action: note>
Sorry about the double text... the first time I rerouted it, CMVC
told me there was a problem and it didn't work...
<Note, action: note>
I checked an IBM LaserPrinter, and the P in Printer is upper.
<Note, action: return>
The names of IBM LaserPrinters do have tradmark errors in Laserjet
driver. Unfortunitily, we can not change them. Otherwise, mix use
of laserjet drivers with different versions in the lan envirnment will
generate errors.
ΓòÉΓòÉΓòÉ 2.200. *60776 BETA: Child windows in AWS eat up 8 meg of shared address sduplicate ΓòÉΓòÉΓòÉ
name 60776
reference
abstract BETA: Child windows in AWS eat up 8 meg of shared address sduplicate
state closed
severity 3
answer dsai
symptom prf
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
BETA: From Mark Cates and David Jeans at SAS institute. Creating child
windows in a application worksspace uses up to 8Meg of shared memory for each
child window created. SAS sent us sample software to illustrate this, which
has been turned over to Rick Thompson to chase down.
<Note, action: modify>
Screen Team Approved
<Note, action: note>
Changed from a single very larg segment to multiple segments
in the segment store.
Rick Thompson 982-XXXX
ΓòÉΓòÉΓòÉ 2.201. 60783 BETA:Help does not function when diskette drive b: noduplicate ΓòÉΓòÉΓòÉ
name 60783
reference
abstract BETA:Help does not function when diskette drive b: noduplicate
state canceled
severity 4
answer intit
symptom fnwad
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
BETA: I have no diskette drive b on my system. If I open the drives folder
and double click on drive b icon, I get popup about putting a diskette in
the drive. This popup has a help button. If you push the button, nothing
happens. I should see a help screen.
The GA version put up a different error message, and the help button does
function on that popup.
Please transfer this to the correct component if I have picked the wrong one.
<Note, action: assign>
This defect was written against the wrong component. I am transferring
it to the message file.
<Note, action: return>
This is a prompt message. Prompt messages do not have
helps. Working as designed. Anita 2-XXXX
<Note, action: assign>
Spoke to Mindy Pollack in Development. This is a hard error
and should be reassigned to SSMG. Anita 2-XXXX.
<Note, action: reopen>
This problem was inadvertantly returned to me. It should be re-opened.
It is a regression from the 2.0 GA product. The user sees a different message
than before which may be okay, but the popup has a help button and that
button does nothing. In the GA product, the help button gives you a help
screen.
<Note, action: return>
Bob, this problem is not a regression from GA. My developer talked
this over with Paul Cheatham and we will TRS to the next release.
Please talk to Paul before rejecting this answer. THANKS!
<Note, action: cancel>
I've cancelled it, but it is truly a regression from GA. In the same
scenario, the GA product puts out a different message and the help button
does give you a help screen. In this version, you get a different message
and the help button is inoperative.
ΓòÉΓòÉΓòÉ 2.202. 60788 BETA: Machine Hangs at OS/2 logo after boot mgr screen ΓòÉΓòÉΓòÉ
name 60788
reference
abstract BETA: Machine Hangs at OS/2 logo after boot mgr screen
duplicate
state canceled
severity 3
answer
symptom vis
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
Machine hangs at OS/2 screen after selecting partition to boot
from boot manager menu. If user hits reset button on PC (not
CTRL-ALT-DEL) machine will boot fine from subsequent boot mgr
screen selection.
Configuration is as follows:
Milex MAE486 33mhz system unit
Milex SCSI DCE376 controller
Fujitsu 500mb hard disk
GSI model 11 floppy controller with
1.2 mb, 1.44mb and 2.88 drives attached
Milex GLE911 video card with 1mb ram
using vanilla VGA drivers.
Future domain 850 SCSI with texel 3024 CD Rom
PAS - 16 board nothing attached
Serial card with COM1 and COM2 ports (Tiawanese $20 special)
Parellel board - LPT1
<Note, action: modify>
Screen Team Approved
ΓòÉΓòÉΓòÉ 2.203. 60797 SVT REG: TRAP E during execution of Rexx ΓòÉΓòÉΓòÉ
name 60797
reference
abstract SVT REG: TRAP E during execution of Rexx
duplicate
state closed
severity 2
answer chki
symptom thipe
duplicate defects:
duplicate features: none.
notes:
<Note, action: open>
Customer Impact: The system is trapping
Hardware: Model 95
<Note, action: note>
Reproduce the problem: Install the driver as normal. Add
the following to the config.sys: set lib=hellolib
set tmp=hellotmp
set include=helloinc
Reboot the system. Execute a batch file called RXRGSTR1. A
trap E is generated. You must power OFF the system to restart
your system.
For more information contact Bernice W. Graham
<Note, action: return>
This problem could not be reproduced in the lastest BORG build driver
level 6.490 .
<Note, action: modify>
Screen Team Approved
<Note, action: note>
The problem still exist on driver 6.494 and 6.496. Attached is
a snapshot of the defect.
<Note, action: note>
Invalid Data is passed in the DS register. The trap is in REXX.DLL at sys_free
within the REXX and PMREXX component. The following information is supplied:
The Rexx.DLL is trapping due to incorrect checking of the length of the
Rexx string being freed and in processing default strings. The problem
has been corrected and a new Rexx.DLL is being integrated.
ΓòÉΓòÉΓòÉ 2.204. 60805 Orchid Prodesigner 2S goes out of sync after diskette 19 ΓòÉΓòÉΓòÉ
name 60805
reference
abstract Orchid Prodesigner 2S goes out of sync after diskette 19
duplicate
state canceled
severity 3
answer invinf
symptom vis
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
During selective install, Orchid Prodesigner 2S display goes bananas
after diskette 19. Messages say - Changing configuration......Checking
Adapter setup...., then the display starts getting squiggly lines..,etc.
When a reboot is performed, the system comes up in VGA mode. Customer
has tried the DSPINSTL command but still fails.
<Note, action: return>
This defect should be updated with more information.
If you could get in touch with your customer and ask the following
questions:
What are the video subsystem statements for VIO_VGA or VIO_SVGA
and VDM video driver like? Are BVHSVGA and VSVGA statements
present? Second, when SVGA WHO executed in DOS full screen, does
it successfully identify the adapter as Tseng ET4000? If so,
when running SVGA ON, is SVGADATA.PMI file generated properly,
and does it list all expected resolutions (256 color and 16 color)?
If so, after the file is generated and VGA desktop rebooted, is
SVGADATA.ERR file present on \OS2 directory? If so, what does
it say. Also, since the installation abruptly stopped, could it be that
there was no room left to copy BVHSVGA and VSVGA onto the hard disk?
And what exactly did you mean by DSPINSTL failed as well? In what
fashion and at which point?
Please, contact me at 3-XXXX if more information needed.
<Note, action: cancel>
Contacted customer and he indicated that he's too busy to send
the information we need to continue on this, so we may as well
cancel it.
<Note, action: modify>
Screen Team Approved
ΓòÉΓòÉΓòÉ 2.205. *60810 Help button on display driver window doesn't work ΓòÉΓòÉΓòÉ
name 60810
reference
abstract Help button on display driver window doesn't work
duplicate
state closed
severity 3
answer asni
symptom fnwad
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
If one attempts to use DSPINSTL either by command line or
through selective install, the help button on the window does
not work.
<Note, action: accept>
Help for display resolutions box was being handled improperly. Fixed
by recreating help instance and letting the help manager process help
messages.
<Note, action: modify>
Screen Team Approved
ΓòÉΓòÉΓòÉ 2.206. *60814 BETA:Migrated config.sys shows FEAT in IFS= statement and tduplicate ΓòÉΓòÉΓòÉ
name 60814
reference
abstract BETA:Migrated config.sys shows FEAT in IFS= statement and tduplicate
state closed
severity 3
answer chkm
symptom fnwad
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
BETA:User Nelson Chen In Boulder has reported his migrated config.sys has
FEAT inserted in some config.sys statements. Specifically IFS= shows
FEAT: <\FDISK> and also SET BOOKSHELF= has FEAT:;<\TUTORIAL>. This leads
to a trap e on boot.
Craig Bennett has the config.sys and install logs and asked me to write
a defect for the problem. He said he knows the fix.
<Note, action: note>
The problem was caused by two threads accessing the same global memory at the same time - one to log output and the other to update CONFIG.SYS. The log routines were debug statements that were interspersed with valid output, so these were removed.
ΓòÉΓòÉΓòÉ 2.207. 60816 BETA: Drive A icon notebook settings can not be opened ΓòÉΓòÉΓòÉ
name 60816
reference
abstract BETA: Drive A icon notebook settings can not be opened
duplicate
state canceled
severity 4
answer invwad
symptom fnwad
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
You can not open the settings notebook on the Drive A icon
without having a diskette in the drive.
<Note, action: return>
This is a duplicate of cancelled defect 25502. You cannot
open the settings view of an empty disk drive because the
details page requires reading the drive. You get a hard
error saying that the drive is empty. This is working as
When setting the background color to other than the default - it
will not stay - upon rebooting the default background color is used.
NOTE>> On the 488 drop trying to set the background color allowed
me to go into the settings notebook ONCE - then upon exiting I
could not go into it again and I could not access the drive.
<Note, action: return>
The first part of this defect, that settings are not saved for
CD drives across re-boots, is due to the fact that CD drives
are read-only. Ideally, we should put up some sort of message
when the settings notebook is opened for a read-only drive
saying that the settings will not be saved after re-boot.
We don't want to entirely disable settings because some people
leave their machine powered on for long enough periods of time
for the settings to be useful to them.
We would like to consider this for the next release.
As for the second part of your note, the error is caused by
a divide by zero exception (already reported in defect 60064).
and only shows up in the post 6.479c beta drivers.
Please accept this to be trs-ed. --Sheila 2-8252
ΓòÉΓòÉΓòÉ 2.232. 61228 CAT & Mouse About Box In Error ΓòÉΓòÉΓòÉ
name 61228
reference
abstract CAT & Mouse About Box In Error
duplicate
state canceled
severity 4
answer asnit
symptom vis
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
The "about box" for Cat & Mouse says "PMSeek" instead of Cat & Mouse.
<Note, action: return>
The copyright screen for cat and mouse says pmseek
instead of cat and mouse. This screen is owned
by development (the person who owns the code).
Please route to development.
Anita 2-XXXX.
<Note, action: modify>
The copyright screen for cat and mouse says pmseek
instead of cat and mouse. This screen is owned
by development (the person who owns the code).
Please route to Joe Tano's (development) area.
Anita 2-XXXX.
<Note, action: return>
This fix requires a change in NEKO.DLG file which is a MRI file.
If the translation can be done for the file, we can make the
change.
<Note, action: cancel>
I understand that this will automatically get opened against the next release.
ΓòÉΓòÉΓòÉ 2.233. 61307 This is to reopen defect 60659 which was closed by me in error. ΓòÉΓòÉΓòÉ
name 61307
reference
abstract This is to reopen defect 60659 which was closed by me in error.
duplicate
state canceled
severity 3
answer invinf
symptom thipe
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
This is to reopen defect 60659 which was closed by me in error.
Sorry.
<Note, action: return>
Why did you reopen this Red ? There was a code change for the last defect, that went into 6.490. Is there a problem with that change ? If so, what ? Returning user error - insufficient info. Paul.
<Note, action: reopen>
This is to reopen defect 60659 which was closed by me in error.
Sorry.
Paul,
It wasn't/isn't clear to me from the text of 60659 that a fix
had been made. It was in the verify state. This is all probably
due to my lack of CMVC expertise. I just don't want the problem
to get lost. I closed 60659, I'm not sure what I should do with
it when it's in the verify state. My notes say my options are
accept, reject or abstain all of which close the defect.
If it is fixed, I wll close this one. Plz advise.
Sorry for the confusion, just don't want to lose it.
Publishers Paintbrush for OS/2 from Zsoft, has a memory error loading large BMPs or GIFs. Memory sometimes locks and OS/2 halts.
The second file loaded of any type causes error in memory. I have a copy of the software and a debug terminal! Sorry if this doesn't
belong to kernel..I did not know were else to send it. <SHR>
<Note, action: modify>
Screen Team Approved
<Note, action: cancel>
Canceled Per Virtual Memory Function of PUBPB in error, defect
will become wpshl comp. <SHR>
ΓòÉΓòÉΓòÉ 2.254. 61516 BETA: color palette needs to change color 'system wide' ΓòÉΓòÉΓòÉ
name 61516
reference
abstract BETA: color palette needs to change color 'system wide'
duplicate
state canceled
severity 4
answer intit
symptom vis
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
Color Palette system wide change does not operate the same as
FONT palette. In Color Palette taking the paint brush to the
desktop -only changes the desktop. If brought to the windows then
all windows change but not the desktop. FONT changes the desktop
and all the windows. Consistency is what is needed.
<Note, action: note>
The problem is that when you drop a color on the desktop,
it changes the background color setting for the desktop, and
there is only one desktop. When you drop a
color on a window, it changes the window color setting, which
is different than the background setting for the desktop.
There is only one font setting. So a system wide font change
changes the fonts on the desktop and all windows.
<Note, action: return>
This has always worked this way, and probably needs to be
changed so it is more consistent. This was not approved by
the PTR reviewers as a ship issue for Borg. We will TRS
it for now and consider for the next release. -Sheila 2-XXXX
<Note, action: cancel>
done in a later release
ΓòÉΓòÉΓòÉ 2.255. 61518 BETA: SETBOOT /Q ΓòÉΓòÉΓòÉ
name 61518
reference
abstract BETA: SETBOOT /Q
duplicate
state verify
severity 3
answer docm
symptom use
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
Subject: SETBOOT /Q
In the on-line Command Reference, if you look at the description of the "/Q"
parameter for SETBOOT, it tells you:
Queries the currently set startup environment. Returns the default
partition alias, timeout value, mode and drive letter assignments for
unattended operation.
To query the current startup environment, type the following:
SETBOOT /Q
Well, here's what *really* happens (cut from an OS/2 Window):
ЫC:\|setboot /q
Timeout 10
System Index 0
Mode advanced
System 0 None
System 1 None
System 2 None
System 3 None
System 4 None
I don't know if the documentation or the command is wrong, but the "mode and
drive letter assignments" would be nice.
A Beta Tester
For additional info, please contact Sheila McDonald-Rich on 3-XXXX.
<Note, action: return>
Do Not use the IDEV component. It is the parent component for all the toolkit information. It has nothing to do with any ship-group documention. I spoke with the Command Reference writer and he says the information matches the code. If there is a prob
lem with that, write the defect against the code.
<Note, action: reopen>
This is being reassigned because it does not appear to a documentation
problem.
<Note, action: assign>
This defect should go against the Command Reference.
<Note, action: return>
I believe this parameter is working as designed. The mode is normal/advanced
the drive letters would be listed opposite the system IDs if there were
any to list.
Vince Spadea ID 2-XXXX
<Note, action: reopen>
Vince,
Per my conversation with Jamie, the documentation for Setboot /Q
is incorrect and needs futher clarification. He will call you with
further information.
Thanks,
Sheila McDOnald-Rich
<Note, action: modify>
Screen Team Approved
ΓòÉΓòÉΓòÉ 2.256. *61543 BETA:Names with period on HPFS system create duplicate foldduplicate ΓòÉΓòÉΓòÉ
name 61543
reference
abstract BETA:Names with period on HPFS system create duplicate foldduplicate
state closed
severity 3
answer dsai
symptom vis
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
BETA: If you create a folder with a name that includes a period in the last
position on an HPFS system, you wind up with duplicate folders.
This problem was found by Mike Turner (2-XXXX) and seen by Mindy Pollack
<Note, action: modify>
Screen Team Approved
ΓòÉΓòÉΓòÉ 2.257. 61549 BETA: Presparams not carried to PS ΓòÉΓòÉΓòÉ
name 61549
reference
abstract BETA: Presparams not carried to PS
duplicate
state canceled
severity 3
answer invwad
symptom fnwad
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
The best way to describe this problem is with an example. Suppose
you have a dialog template that looks like this:
DLGTEMPLATE ID_DIALOG
BEGIN
DIALOG "sample dlg", ID_CONTROL, 10, 10, 100, 10
PRESPARAMS PP_FONTNAMESIZE "8.helv"
PRESPARAMS PP_BACKGROUNDCOLORINDEX CLR_DARKBLUE
PRESPARAMS PP_FOREGROUNDCOLORINDEX CLR_WHITE
BEGIN
......
END
END
In your dialog the text will be drawn in the correct font and colors.
The correct font is used because the system applies the font to the
PS before returning from WinGetPS or WinBeginPaint. The colors are
correct, however, because the window receives a WM_PRESPARAMCHANGED
for colors, and the color is remembered in the instance data. You
can see the difference if you use a piece of code in your dialog
The reason this worked in GA is because we had a bug where
commas were treated as commas always and there was no
way to set multiple dos versions or multiple dos devices (shown
with line feeds in the dos settings dialog). The way this was
fixed is as follows: when you specify a dos setting for a
setup string, use comma to represent a separate setting for
the keyname (ex. SET DOS_DEVICE=DEVICE1,DEVICE2)
and a comma with a '^' in front to represent just a plain comma.
(ex. SET DOS_VERSION=123DOS.exe^,3^,40^,255)
So the test case in this defect should have '^'s in front of every
comma that was intended to be an actual ',' in the dos setting.
--Mindy Pollack
ΓòÉΓòÉΓòÉ 2.352. 63290 BETA: parameter settings disappear on reboot ΓòÉΓòÉΓòÉ
name 63290
reference
abstract BETA: parameter settings disappear on reboot
duplicate
state canceled
severity 3
answer valunr
symptom vis
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
This was tried on settings of \os2\cmd.exe.
<Note, action: modify>
DO: OS/2 system; Drives icon; drive where OS/2 resides;
open OS/2 folder; click on CMD.EXE with RMB to open settings;
enter % in parameter field; close all of these windows.
Go to Desktop Settings Notebook and add a Prompt menu to the
Desktop Menu. Use Command Exe as the title, and \os2\CMD.EXE
as the program to execute. If the % sign is present in the
parameter field when this new menu selection then NO error msg
is displayed when the window is started. If the % sign is not
present an error msg is first displayed and then the window starts.
However - on a reboot the parameter field was cleared and the
error message was once again present when the prompt selection
was started. This scenario did not occur if I used the command
prompt icons to add prompt selections to the menu. The % sign
in every case ( DOS full, DOS window, OS/2 full, OS/2 window )
remained after a reboot.
<Note, action: modify>
Screen Team Approved
<Note, action: note>
I tried this on 6.498b and it seems to work fine. Reboot. use prompt on menu - window popsup with no error. Check the parameters of cmd.exe's file object and it still contains %
I'll probably return unreproducible, but i'd first like to see it fail. I'll call Richard.
<Note, action: return>
Couldn't reproduce on 6.498b.
Jon Grimm 2-XXXX
<Note, action: reopen>
I was able to reproduce the error on 6F.498.
Notified Jon Grimm that I would show him the error on my
terminal.
<Note, action: return>
Richard and I tried to reproduce this on 6.498G in my office and in their lab. Also tried 6.498F in their lab. Still unable to reproduce this to debug.
Jon Grimm 2-XXXX
ΓòÉΓòÉΓòÉ 2.353. 63343 Large Rex Programs Do Not Erase Unused Extended Attributes ΓòÉΓòÉΓòÉ
name 63343
reference
abstract Large Rex Programs Do Not Erase Unused Extended Attributes
duplicate
state open
severity 4
answer
symptom use
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
Note:
I have talked with Jeff Gray at IBM Endicott about this Rexx Defect.
Mike Jasinski
----- OS2BETA FORUM appended at 15:57:48 on 93/03/03 GMT (by V$IBITG7 at BCRVMPC1)
Subject: Rexx and EA's
Ref: Append at 01:11:29 on 93/03/02 GMT (by KOLSKY at YKTVMH)
Amir,
The limit of 64KB for a tokenized image to get stored in an extended
attribute is documented in the OS/2 2.0 Procedures Language 2/Rexx
Reference pgs 2-18, 2-19 "Running a Rexx program".
The problem is really a design issue, not a Rexx problem. The behavior
in question is why doesn't Rexx clear out the unused extended
attributes of a Rexx program whose tokenized image is greater than
64KB. When Rexx runs a rexx cmd file, it stores a tokenized image in
the file's EAs (on an HPFS system), unless the program is so large
that the image won't fit in the EA space. When this happens, Rexx can
no longer store and re-use the image in the file's EA, so it must
re-tokenize each time the program is re-run. The issue then becomes
why Rexx doesn't release the EA space is doesn't use and I believe
this is a design issue, not a defect. This is primarily due to the
documented restriction in the Rexx reference and the recommendation
for better performance to break up large Rexx programs such as these.
The test case that was given has an error, the 7th line should be
'call a >> c3000.bfr' , not 'c3000.pre'. The test case is showing on
an HPFS system that a tokenized image is stored in a file's EA, and
when a rexx program is made large enough(ie. c3000.bfr), the image
still exists even though Rexx no longer uses it.
This situation works the same way on GA, servicePak, and the latest
BORG driver.
Mike Jasinski Boca Technical Interface Group
----- OS2BETA FORUM appended at 19:34:20 on 93/03/03 GMT (by HALLERMA at BCRVMPC1)
Subject: Rexx and EA's
Ref: Append at 15:57:48 on 93/03/03 GMT (by V$IBITG7 at BCRVMPC1)
No, you should log this as a defect.
Failure to free up unused or discarded space is a performance/dasd space
defect just like the ram memory leak defects.
Mel Hallerman
<Note, action: modify>
Screen Team Disapproved
ΓòÉΓòÉΓòÉ 2.354. 63426 BETA: VXGA.SYS not found after Selective Instl. on RADIUS duplicate ΓòÉΓòÉΓòÉ
name 63426
reference
abstract BETA: VXGA.SYS not found after Selective Instl. on RADIUS duplicate
state returned
severity 3
answer valunr
symptom use
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
The following problem is happening only on non-IBM systems:
Systems with a RADIUS XGA-2 card work fine using XGA
resolution. If a selective install is done to change video mode and
XGA is selected, then when rebooting and error occurs loading
VXGA.SYS in CONFIG.SYS. The file VXGA.SYS does not exist in
the harddrive anymore. The file is copied back in the harddrive after
doing a selective install for the DOS component.
<Note, action: modify>
Screen Team Approved
<Note, action: return>
Not reproducable in 6.498.
ΓòÉΓòÉΓòÉ 2.355. 63466 BETA: Font reverts back to sys proportional after reboot ΓòÉΓòÉΓòÉ
name 63466
reference
abstract BETA: Font reverts back to sys proportional after reboot
duplicate
state working
severity 3
answer chki
symptom vis
duplicate defects: none.
duplicate features: none.
notes:
<Note, action: open>
Open the font palate and OS/2 System Window on desktop. Select
Times Roman 8pt with LMB. Using Alt-RMB drag Tms Rmn font
onto the System Menu Button attached to the OS/2 System Frame
Window. This will globally change the font for pulldown and popup
menus to Times Roman which it infact does. The popup menu for
the OS/2 desktop is changed also as expected. But if we shutdown
and reboot the font for the desktop popup menu has reverted back
to the default System Proportional Font.
<Note, action: modify>
Screen Team Approved
<Note, action: note>
Changed the wasy we set the presentation parameter in the
LoadContextMenu procedure. We now query the profile string
using the global font variables and then set the presentation
parameters appropriately. Previously we "mucked"
around until we got the reight pres params. (?) Roberta 3-XXXX
(.txt)