Scope
General
System
requirements
Build
information
Whats
new
Known
issues
Scope
This document states the known issues and
bugs of the software released.
General
System requirements
- Pentium II 266MHZ
- 1MB free disk space
- OS: Windows 98 Second edition, Windows
2000 or Windows XP
- Latest DiskOnKey driver installed
(Windows 98)
- Administrative privileges (Windows 2000
and Windows XP)
Build information
For
internal use only:
|
Component
|
Version
|
Comments
|
|
DOKSDK
|
|
|
Whats new
Build
3.2.8.18
Customization Verbatim Updated
customization of splash screen.
Build
3.2.8.17 (& 3.2.8.17 - Plus)
Bug fix #3369 - Wrong used space after
formatting 4GB device to maximum privacy zone size.
Bug fix #3393 - Can't set size of privacy
zone to maximum on a 4GB device on Win 98.
Bug fix #3366 - 4GB device won't contain
the application when format to maximum privacy zone size.
Note: All bugs above are based on a low-level
bug (SDK or Firmware) on privacy zone creation on 4GB devices when the privacy
zone size is set to the maximum. Our solution is to limit the privacy zone size
to 98% (instead of the previous 99%) of the device capacity. This solution is
only temporary until a final fix will become available.
Build
3.2.8.16 (& 3.2.8.16 - Plus)
Updated SDK.
Bug fix #1604 - Wrong shortcut name.
Bug fix #2990 - The trust option doesn't
work on S1 - rev K device.
Bug fix #2745 - Error message appears
while trying to safe remove a device after removing the privacy zone.
Build
3.0.7.15 (& 3.1.7.15 - Plus)
New SDK, logs removed (used for debugging
and tests).
Build
3.0.6.15 (& 3.1.6.15 - Plus)
New SDK that solves the WinXP SP2 issues
(safe eject fails, device status after write protection and device status after
eject fails).
In addition this SDK includes an improved
2GB devices supports.
Build
3.0.5.15 (& 3.1.5.15 - Plus)
Update Change 'Unable to create Privacy
Zone.' to 'Unable to create Privacy Zone. Please make sure that the key is
not write protected.'
Build
3.0.5.14 (& 3.1.5.14 - Plus)
Customization IO-Data - New
Customization.
Customization Plextor New
Customization.
Customization IBM Change Application
name from 'KeySafe' to 'KeySafe II'.
Build
3.0.5.13 (& 3.1.5.13 - Plus)
Customization Kingston Change Splash screen to with
'TravelerSafe+'.
Customization Kingston Change slider gifs with Gray
background.
Bug fix Kingston Fix text that include
'DataTraveler Elite Elite'.
Build
3.0.5.12 (& 3.1.5.12 - Plus)
Customization Kingston Change Device name DataTraveler to
DataTraveler Elite.
Customization Kingston Change Application name
TravelerSafe to TravelerSafe+.
Customization Kingston Change Slider Gifs.
Customization Verbatim Change Slider
Gifs.
Customization Kingston/IBM Update
slider tooltip.
Build
3.0.5.11 (& 3.1.5.11 - Plus)
Bugfix Adding 'Ignore' String to Kingston
Plus customizations and Languages.
Bugfix Updating the on shutdown message
to all customizations.
Build
3.0.5.10 (& 3.1.5.10 - Plus)
Bugfix Adding 'Ignore' String to all
customizations and Languages.
Build
3.0.5.9 (& 3.1.5.9 - Plus)
SDK fix Supporting devices up to 2GB on
win98.
Bug fix Application are not stuck when
saving in the Privacy zone after suspend.
Bug fix Monitors' shutdown message
always shows OK Button on all OSs.
Build
3.0.4.8 (& 3.1.4.8 - Plus)
SDK fix Supporting devices up to 2GB.
Build
3.0.3.7 (& 3.1.3.7 - Plus)
Monitor flushes drive before force
logout.
Monitor prompts user before shutdown
events.
Bug fix Formatting succeeds in win2k
sp2.
Bug fix Monitor closes all related explorers
before logout.
Customization Eliminate Question marks
in Spanish & Portoguese.
Customization (IBM) Trust CheckBox
changed to white.
Build
3.0.3.6 (& 3.1.3.6 - Plus)
Bug fix Autorun checkbox position is
fixed for different OSs & Customizations.
Customization update - Updated Verbatim
screens.
Customization update Added IBM KeySafe+
customization.
Customization update Update DataStorage
customization.
Build
3.0.3.5 (& 3.1.3.5 - Plus)
Bug fix FixSafe for 1GB devices.
Bug fix No error message creating trust
with a changed EXE filename.
Bug fix increased minimum of public
zone to 2MB.
Bug fix monitor doesn't exit
unexpectedly.
Bug fix monitor closes related
explorers when resuming from hibernate.
Bug fix trust checkbox is reflect correct
state after untrust message box.
Bug fix One error message when there's
a corrupt trust token.
SDK fix KeySafe works with CD+Removable
configuration.
Customization Shortened trust string of
trust checkbox.
Customization Added translation of new texts
for all languages.
Customization Replaced some Asian texts
for IBM.
Customization Replaced German text for
IOData.
Build
3.0.2.4 (& 3.1.2.4 - Plus)
Bug fix No logout after login in
3.0.2.4.
Build
3.0.2.3 (& 3.1.2.3 - Plus)
Bug fix Fix safe Support.
SDK fix Support T3.
Hint supports multiline.
Support file copy in monitor mode.
Build
3.0.1.2 (& 3.1.1.2 - Plus)
All bugs are fixed
Autorun is now referring to section
Launcher PC (as the Autoruner) in the Autorun.inf file
The Autorun does not use the
'auto' suffix
Build
3.0.0.1
SDK 4.2.
Login/Logout confirmation are now stored
as cookies (will behave the same way on different computers)
Desktop/Quick Launch check-box are now
referring to the actual icon instead of the ini file.
Language is now stored on cookie.
Added real check-box support (you can now
check/uncheck be pressing the text too).
Added tooltip to checkboxes in settings
dialog instead of the description box.
Added mechanism to re-enter password in
case the deposit disappears.
Disabled support for winME.
Added support for win2K3
KeySafe now runs in CD & Removable
devices (CD & Secured is still disabled).
Build
2.5.10.13
Bug fix- pulse for win ME at the
application instead of SDK.
Build
2.5.9.12
Bug fix for I-O Data & Fuji- Insert
missing texts.
Change in Release notes line of build
2.5.4.5
Build
2.5.9.11
Bug fix- refreshing while moving the
slider.
Build
2.5.9.10
SDK fix- eliminate magic numbers for T3.
Build
2.5.8.9
SDK fix- eliminate magic numbers.
Build
2.5.7.8
SDK fix- eliminate magic numbers.
Build
2.5.6.7
SDK fix- eliminate magic numbers.
Build
2.5.5.6
SDK fix- eliminate magic numbers.
Un-workaround of SDK bug that was fixed.
Build 2.5.4.5
SDK fix- turning MBR to inactive.
Build
2.5.3.5
Kingston
fix- fixed spelling on shortcut on desktop to 'TravelSafe' instead of
'Travelsafee'.
Kingston
fix- changed description text of privacy zone to indicate red instead of
orange.
Bug fix- device sizes are shown and
updated in setting window in traditional Chinese.
Build
2.5.3.4
Fixed WinME format privacy zone to 0
(zero).
Build
2.5.3.3
SDK version number 4.0.0.31 with fixing
of the following bugs:
FW bug: Failed to format when the
device plugged in without privacy zone.
Fix bug: Cant convert old cookies
that have been written by old SDK on Win ME.
Cancel sleep after enter wrong password.
Update customization for all vendors.
Replace error icon with exclamation icon
when erase the privacy zone
Build
2.5.2.2
New SDK for T4 version number 4.0.0.29
After enter wrong password, on login or
change password, the windows button and password edit text will be disable for
3 seconds meanwhile a wait cursor will display.
The app supported WIN ME.
Fix text in Japanese.
Fix again flickering slider (decrease
slider image in one pixel).
Fix bug with FW 4.01 and 4.20.
Build
2.5.1.1
New SDK for T4 version number 4.0.0.22
Change Slider scrolling mechanism:
1.calculate fix size only when
finish to scroll the slider.
Increase the range of the slider
to 107 (for Generic application for other maybe need different factor).
Fix the Slider to stay in is place after
format. (bug number 1033).
Fix bug: On win 98 failed to format on
T2.
Fix bug: Failed to format FW 2.71.
Not support WIN ME.
Build
2.5.0.0
New SDK for T4 version number 4.0.0.17
Support MAX NOA.
Fix bugs - dannyd-nt5nshareKeySafe
Build
2.3.6.33
Release for Fujifilm.
Change from Key Safe to Sentinel in
German ( fix this bug in all the other customer).
Build
2.3.6.32
Release for Fujifilm including the
following changes:
Add fuji
Icon.
Change slider background to fuji color
Change background for logout text in
windows explorer from orange to fuji
blue (same blue used in slider).
Replaced KeySafe with Sentinel.
Replaced DiskOnKey with Fujifilm USB Drive
Change orange to light blue.
Build 2.3.6.31
The same as 2.3.6.30 with fix of the
following bugs:
Bug number 750: Unable to format 768mb
device to special size 517.41 (
Remove the comment from the function GetFixFormatSize()).
Remove M-Systems from the setting
dialog and the splash windows.
Replace the word DiskOnKey with
EasyDisk
Build 2.3.6.30
New SDK (3.1.2.14) solves 1gig DiskOnKey
format problem.
Capacity exceed the device actual
capacity
Build 2.3.5.30
New SDK (3.1.2.12) appropriate for T4.
Release for IO-DATA.
Fix of the following bug:
The image in format windows is flashing
under Win Me
The applications double the privacy zone
(FW bug).
In Win 98 JIBRISH character is seen in
application properties.
Build 2.3.4.29
New SDK (3.1.2.11) appropriate for T4.
The application will work in user mode
without a problem to create Short Cut (Also on Win Me ,Win 98 & Win2K SP
1,2,3).
Release for IO-DATA.
Build 2.3.4.28
Fix bug : Shortcut didnt create on WinME
- used CoInitilize to WinMe &
Win98 , and CoInitilizeEx to Win2K & Win XP.
Build 2.3.4.27
Remove icon change for IBM (this fix
somehow got lost).
Build 2.3.4.26
Verbatim text changes.
Build 2.3.4.25
KeySafe supports DiskOnKey access service
(for Win2k and WinXP) to overcome the admin problem. The service was added to
the project in the version management.
Build 2.3.4.24
Verbatim text changed (orange to blue) +
DOK image in format screen is now blue.
Build 2.3.4.23
Verbatim text changed (Store n Go à StorenGo, V-safe
à V-Safe).
Change password dialog caption fixed (now
states the application name instead of Dialog).
Build 2.3.4.22
KeySafe for disgo.
Fix bug: the DOK image flickering while
move the slider.
Build 2.3.4.20
KeySafe for disgo (text and GUI changes).
Fujifilm icon change.
Release build with the new SDK (3.1.2.6).
Bug fix- you can now format 8MB DiskOnKey
to max or min (you may not get the exact requested size but the closest
available instead).
Bug fix when no DiskOnKey is found the
message will popup in front of the splash screen.
Build 2.3.4.19
KeySafe for Disgo ( Change GUI).
SDK 3.1.2.6
Build 2.3.4.18
KeySafe ,IO-DATA,IO-MEGA release.
SDK version number 3.1.2.6.
Change gif for IOMEGA.
Remove drive Icon for IO-DATA. This
change done for IO-DATA in previous version ( PATAGONI PRO ) but not update in
PATAGONI 2.X versions.
Fix bug : Cant destroy the privacy zone
2.51 128MB.
Build 2.3.3.15
KeySafe generic release.
SDK version number 3.1.2.5.
Build 2.3.2.14
Fix GUI ( Slider not I focus).
Build 2.3.2.13
Change GUI for IBM.
Use a16 pt Ariel bold font for the
title Setting Memory Keys Privacy Zone on format dialog and Current
Setting on setting dialog.
Made the slider background transparent.
Change the color of the Dont
show this message again text, on the select language from white to black.
Replace error, exclamation and
information gif with blue background
Add KeySafe IBMs icon files
contain 48 x 48 pixel version.(look better on window xp).
Fix bug: KeySafe fails to format the 2k
page DOK to the following size 4.88; 21.96; 31.72; 41.48; 43.92; 51.24; 53.68;
73.20; 82.96; 136.64; 143.96; 146.40; 153.72; 156.16; 163.48; 165.92; 185.44.
SDK version 3.1.2.4
Build for Sony.
Build 2.3.1.12
Change Company Name to customizes company
name instead of M-Systems. For example change to IBM company name instead of
M-Systems.
Build 2.3.1.11
GUI fixing in IBM release.
Build 2.3.1.10
Release for IBM include changes of GUI
such as: string color, button size etc (All that changes made by preprocessor
define).
Add string table in Portuguese.
Fix bug: format does not zero KeySafe failure count.
Change IDS_MSG_SIZE_DESCRIPTE to be as
same as the string in English. (
cause we do not have transl ating to
this sentence in all language)
Add isWorkableDOK function that return
true if the DOK is IBMs DOK and FALSE
else.
Build 2.3.1.9
Release for FujiFilm.
Fix bug: The logout dialog open under the
explorer window.
Fix bug : The splash window open under
the other window.(this bug was fixed before but put in comment)
Build 2.3.1.8
Release for FujiFilm.
Fix bug: The dailog does not paint
properly in the Japanese
Build 2.3.1.7
Release for FujiFilm.
Build 2.3.1.6
Release for FujiFilm.
Fix bug : The refreshing DiskOnKey image
is not working roperly.
Build 2.3. 1 .5
SDK 3.1.2
Fix bug: The windows open on the bottom
of the other open window
Build for fujifilm
Build 2.3.0.4
SDK 3.1.0.0
Build 2.3.0.3
SDK 3.0.10.8
Customize for IBM
Add Portuguese language for IBM.
Fix bug Cant format for max capacity in
8MB.
Fix bug- large fonts: Lines cut in change password dialog window
Fix spelling error in IOMEGA.
Build 2.3.0.2
SDK 3.0.10.6
Build 2.3.0.1
Change copyright for M-Systems.
Change from KeySafe to Mini Lock in
Iomega release.
Change from DiskOnKey to Mini USB Drive in
Iomega release.
Build
2.3.0.0
DOKSDK version 3.0.10.4
Addition special message for old version
of DOK (less than 2.50) that does not supported by the KeySafe.
Fix the progress function to appropriate
with the DOKSDK version.
Build
2.2.18.25
Added USB 2.0 support.
Build
2.2.17.25
Bug fix - IO-Data, the change password
button was removed.
Build
2.2.17.24
Bug fix Fujifilm disk 3.041 used on Win
98. KeySafe will now recognize the Fujifilm disk.
IO-Data, the change password button was
removed.
Build
2.2.16.23
Bug fix Fujifilm disk 3.x used on Win
ME. KeySafe will now recognize the Fujifilm disk.
Bug fix the change password button is
reachable with TAB key.
Updated Japanese translation for
M-systems, Fujifilm, IO-Data and Acer.
Bug fix change password allows the user
to enter 32 signs hint (the previous version ignored the hint if it was 32
signs).
Bug fix in the logout window the OK and
Cancel buttons have space between them.
Bog fix device removal window will now
be closed in all languages.
Added Chinese translation (Traditional
& Simplified) to M-Systems build only.
Build
2.1.15.22
Bug fix Fujifilm disk 2.x used on Win
ME. KeySafe will now recognize the Fujifilm disk.
Bug fix Change password, fixed password
length for compatibility reasons with FW 3.x.
Bug fix SDK unload problem on Win
ME/98.
Bug fix Change password on FW 3.041.
Added translated text for the new text.
Build
2.1.14.21
Bug fix no logout confirmation is
checked, logout fail the application did no unload.
Bug fix fixed disk Windows Explorer not
closed if partition is not recognized (the identifying file is missing after
OS drive format).
Build
2.1.12.20
Added the ability to change the password
without format.
Fixed - FW 3.x DiskOnKey identification,
KeySafe will now recognize all DiskOnKey with FW 3.x of all partners.
Build
2.1.10.19
Bug Fix DiskOnKey FW 2.01 does not
stack the application.
Build
2.1.9.19
Cookie corruption (hint was lost) bug
fix.
Format Titan removable disk to small size
bug fix.
Build
2.1.8.19
Bug Fix KeySafe now recognize Fujifilm
DiskOnKey on windows ME.
Bug Fix DiskOnKey FW 2.01 does not
stack the application.
Bug Fix DiskOnKey FW 1.08 does not
stack the application.
Bug Fix Hint is again 31 characters
instead of 15.
Build
2.1.7.18
Read only bug fix (from Sony). If KeySafe
file was set to read-only mode the application will fail to launch.
Magic numbers bug fix. Magic numbers
are numbers of bytes that stack the format process.
Cookies compatibility with MyKey.
Missing text in translated languages. The
text will be in English.
KeySafe Zone drive icon bug fix (Sony).
Build
2.1.6.16
Chinese translation.
Build
2.1.6.12
Version format is now x.x.x.x.y.y
(x.x.x.x application version, y.y DiskOnKey version).
If the user tries to create a Privacy
Zone too small for the DiskOnKey, the size will be set automatically to the
smallest possible value (user asked for 77KB, minimum allowed is 400KB the
Privacy Zone will be set to 400KB).
If the user tries to create a Public Zone
too small for the DiskOnKey, the size will be set automatically to the smallest
possible value (user left 77KB, minimum allowed is 400KB the Privacy Zone will
be set to 400KB).
Added I-O Data application (KeySafe I-O
Data.exe).
New icons.
Build 2.1.2.7
Fixed disk support.
Win98/WinXP/WinME support.
Sony multilingual version adjusted to the
new GUI infrastructure.
Known issues
Build 2.1
When upgrading to a
new version, the user must copy the new file to their DiskOnKey and then
launch it from the DiskOnKey (double click the application) and not to use the
shortcut they have on the desktop or quick launch bar. After the first run all
shortcuts will point to the new upgraded version.
- Privacy/Public Zone visual indication
Icon indication:
The drive icon is replaced with a kangaroo with a lock after first successful
login. Public zone will have a kangaroo icon (no lock). (Not Supported by
Windows XP)
Background
indication: The background colour of Privacy Zone is orange supported by
Windows 2K and Windows XP by default. In Windows 98 their indication is not
seen if user uses classic style view in the Windows Explorer (see Folder
Options).
When using fixed
disk (Titan) the icons will be visible from the second use.
- You can not launch two instances of KeySafe at the same time
Upon launching the
second instance the user will be switched to the first instance of the
application and the second instance will terminate.
- Working with more then one DiskOnKey
If a second
DiskOnKey is inserted the application will warn the user and then terminate.
Note that the
system allocates part of the disk space for its use (the File Allocation
Table). This will always cause the
DiskOnKey to have less memory capacity as advertised.
The application
require ~900KB of the total free disk space.
On some machines
the user may experience refresh problems when logging in and out of Privacy
Zone. (i.e. when a user first logs into the Privacy Zone, the background may
not turn orange (the indicator that the user is in the Privacy Zone) unless
they refresh F5.) Newer Windows service packs will solve this problem.
- Privacy Zone Size must be set on first use
When the user run the application for the first time
(Privacy Zone size is 0), the user must set Privacy Zone size of greater than
1% of total capacity size of the DiskOnKey. Otherwise the OK button is
disabled.
On Windows ME and
Windows98 when you type a wrong password the message will state Unable to
login instead of Incorrect password.
- DiskOnKey is unrecognised when a the disk is not accessible
When running a Disk Utility on the DiskOnKey, like 'Disk
Defragmenter ' or 'Scan Disk' or any other Disk Utility, the
security application KeySafe will be unable to access the disk and be
'ran' from the DiskOnKey. KeySafe is temporarily 'locked out'. After the Disk Utility is finished, KeySafe
will continue to function as normal.
- Switching zones with open documents
Some applications
allow the user to switch zones when they have documents open from the DiskOnKey
(like MS WordPad). If the Zone is switched when the document is open, the
changes made will be saved on the other Zone.
- DiskOnKey first use on a computer
The user must wait
for a new DiskOnKey to finish its registration with Windows before launching
KeySafe.
- After 5 wrong password insertion Format will fail
After the user
provided wrong password 5 times, the application will popup a message telling
the user he must remove and reinsert the DiskOnKey and then the application
terminates. If the user rerun the application without(!) removing and
reinserting the DiskOnKey and he tries to format the DiskOnKey with KeySafe
format will fail.
- Window 2K and Windows XP multi session problem
If the user login
to the secured zone and then logoff the workstation, the other user that will
login the workstation will encounter problems. If the user that originally
logged into the secured zone will login again to the workstation the problem
will stop.
If the system
default local is set to a language that does not support the selected language
character set, the user will see ? instead of the character. A scenario
example, if your default local is Hebrew, you will not see
European languages accent characters. If you default local is English you will
not see Japanese characters.
If the user used a
disk layout utility (like fdisk or Windows2K disk manager) to change the disk
layout, key safe may stop function correctly.
When using fixed
DiskOnKey restarting the computer the DiskOnKey doesnt logout from the Privacy
Zone. To logout the user has to either logout using KeySafe or disconnect the
DiskOnKey from the computer.
- Disconnecting the device during login
When disconnecting
the device during login (about 0.5 second after you press OK) KeySafe doesnt
tell you that the device was disconnecting, and if you connect the device back
in the login might be completed
- Not accurate sizes for BIN device
Most of the sizes that KeySafe claim to format to are
not accurate (Mistake is up to 0.3 MB).
KeySafe formats the
DOK to sizes that don't match exactly the size it says. For example, when
formatting a 256mb DOK (2kp) to the size of 117mb priv. zone it actually
formats it to 116.5 (according to the volume's properties - windows
calculation). Other than that the public zone is also smaller than I would
expect. If you sum up both priv and pub zones you'll be about 1mb short (243mb instead
of 244mb).
- KeySafe's shutdown zeroes KeySafe's failure count
Fail login 2 times
Shutdown KeySafe Run KeySafe and fail login 3 more times. You don't get the message about 5 times wrong password.
If you enter the right password now you'll be told it's the wrong password
- Creating new privacy zone with new hint problem with refresh hint
field
When creating new
privacy zone with different hint and returning to the login window the old hint
is shown for ~5 sec until refresh to the new hint. ) On Win Me only).
- Logoff and leave privacy zone open
If user enters the
privacy zone and logoff without logging of from the privacy zone the next user
(with administrator or guest privilege) can enter the computer and the privacy
zone is open.
- Blue screen when pulling the device after format finishes
Format the DOK.
Click 'OK' on the 'Format successful' dialog and pull out
the DOK right afterwards. You'll get a
blue screen about failing to write to disk. There shouldn't be any writing to
disk after the format completes
