Igromania 1999 December

home *** CD-ROM | disk | FTP | other *** search

/ Igromania 1999 December / 27_12_1999.iso / Soft / nlsetup.exe / FILES / 104 / 104

Wrap

Text File | 1999-11-27 | 25KB | 533 lines

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN"> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> <meta name="GENERATOR" content="Microsoft FrontPage 3.0"> <title>Revision History</title> </head> <body background="Skin.jpg"> <big><big>Revision History</big></big> <hr> <big>3.14e (Release)</big> <ul> <li>Fixed the command-line disconnect and scheduled disconnect bugs.</li> <li>Corrected the mangled exe's that come with NetLaunch. They were compressed with the wrong program when I created the archive.</li> </ul> <hr> <big>3.14e (Beta 4)</big> <ul> <li>Fixed a bug which caused the first item in the second column of a multiple-column context menu inoperable.</li> <li>Corrected the links in the About Box to reflect the current webpage location.</li> </ul> <hr> <big>3.14e (Beta 3)</big> <ul> <li>Changed libraries to use the new Microsoft SDK linker libs (found out why the first 3.14D release failed to load the Prefs screen with the new SDK libs, and fixed it)</li> <li>Streamlined NetLaunch's usage of the registry by cleaning up several redundant checks and moving some settings to memory</li> <li>Created some registry buffer code (much like a "smartdrv" for the Windows Registry). The end result is that you will see much less registry activity, and NetLaunch now no longer polls the registry at ALL.</li> <li>Fixed a beta 1 bug which caused the low-traffic disconnect to fail</li> <li>Fixed a beta 1 bug which caused an exception error when disconnecting (the exception was handled, but an exception is an exception!)</li> <li>Finally nailed down the low-traffic disconnect bug.</li> <li>Moved several language-specific strings to the resources, so they can be easily edited. This is in preparation for the possibility of releasing different language versions of NetLaunch.</li> <li>Went through all the code in order to make it compilable in both UNICODE and ANSI formats. Previously NetLaunch was strictly ANSI. Currently only Windows NT implements a complete UNICODE environment, so a UNICODE version of NetLaunch would only run on NT.</li> </ul> <hr> <big>3.14d (03-30-1998)</big> <ul> <li>Recompiled all the executables, including the installer and uninstaller, using a runtime library I made as a subset to the standard runtime library that is compiled with normal apps. The end result is that all exe's are much smaller.</li> <li>Altered the registry cleanup code to fix an infinite loop occurring on some systems</li> <li>Fixed a notification bug in the Launch List. When NetLaunch was first run after a fresh install in which a previous Launch List was not found, NetLaunch would fail to recognize any new items in the Launch List until NetLaunch was closed and re-started.</li> <li>Fixed a problem NetLaunch was having executing .PIF files. It seems that the PIF file settings were not being used when the DOS program opened up.</li> <li>NetLaunch no longer stores online information in its registry key, but keeps it in memory instead. Basically it means that NetLaunch no longer polls the registry every second to get dial-up networking status.</li> </ul> <hr> <big>3.14c (03-25-1998)</big> <ul> <li>Fixed a bug in the low-traffic disconnect option, which caused NetLaunch to sometimes drop the line immediately after connecting.</li> <li>Added code to "flush" the system tray after closing programs. This will effectively clean out any icons that a program may have left in the system tray after NetLaunch has shut it down.</li> <li>When preparing to launch a program automatically, NetLaunch will re-verify the proper qualifications after the specified time delay has elapsed to see if it should still launch the program. In a nutshell, if you specify a time-delay launch on connect, and the connection is dropped before the program has launched, NetLaunch will not launch the program.</li> <li>Corrected some potential notification bugs that can happen if the Launch List is updated while the Preferences screen is on display.</li> <li>Fixed an icon display problem if a shortcut either was invalid, or did not have an icon associated with it.</li> <li>Fixed a startup bug which sometimes caused multiple instances of NetLaunch to start, and/or caused programs launched through NetLaunch at startup to not properly close later on.</li> </ul> <hr> <big>3.14b (03-20-1998)</big> <ul> <li>Added support for showing/hiding sub-directories (submenus) in the Launch List</li> <li>Added enviornment variable support for assigning the launch list directory. (i.e. "%windir%\Start Menu\Programs\Internet")</li> <li>Added registry clean-up code to keep the NetLaunch registry key from getting cluttered with unused stuff</li> <li>Fixed a command-line bug which caused NetLaunch not to launch programs/connections from the command line. If you are using NetLaunch to execute a program from the Launch List from the command line, you must include the shortcut's extension in the command line parameter or it will not work! This is a change in behavior from the previous versions of NetLaunch, but was necessary to avoid possible filename problems and mismatches when trying to identify the program you are attempting to launch.</li> <li>NetLaunch can now detect the closing of DOS applications, including batch files!</li> <li>Minimum connection speed and low-traffic disconnect are now working for Win95 users who have not upgraded to MSDUN1.2 -- I highly recommend upgrading to MSDUN1.2 anyway!</li> <li>Updated several outdated items in the helpfile</li> <li>Slightly altered my hook procedure (NT4/5 only) which may have been causing a problem if other hooks were installed. (An example would be RTVReco v5.x, which uses hooks to catch windows and dialogs as they appear)</li> </ul> <hr> <big>3.14a (03-15-1998)</big> <ul> <li>Fixed a GP fault when loading schedules into memory under certain conditions</li> <li>Fixed a display bug where DUN connection names with period "." characters were truncated</li> <li>Reverted the tray icon back to the original, and made a new Disabled tray icon that looks better (in my opinion)</li> <li>NetLaunch sometimes didn't redial after disconnecting a connection that failed to meet minimum speed requirements.</li> <li>Fixed a GP fault that sometimes occurred while dialing an ISP, just after the connection is made. Usually happened on NT only.</li> <li>When entering a timeout value for a program in the Preferences screen, if you clicked on another item, it would inherit the previous item's settings.</li> <li>Fixed a "divide error" when bringing up the Preferences screen. Only happened to users on Win95 with COMCTL32.DLL version 4.00.950.</li> <li>Removed the Exit button in Preferences if the system tray icon is visible. If the tray icon is not in the tray, the Exit button will be there so that you can exit NetLaunch completely.</li> <li>NetLaunch was pretty stupid about locating the helpfile...Fixed!</li> <li>NetLaunch failed to shut down or detect previous instances of programs in the launch list that contained period "." characters in the filename (other than the extension)</li> <li>NetLaunch sometimes wouldn't let NT4 shut down properly, instead you had to exit NetLaunch manually before NT4 would shut down</li> <li>Fixed a GP fault in Dial-Up Networking that happened when NetLaunch was started, a connection was made and then broken, then NetLaunch was closed and restarted, and a connection was made again. (This one was a bit difficult to fix!)</li> </ul> <hr> <big>3.14 (03-13-1998)</big> <ul> <li>Sorted the Launch List and Connections in the context menu</li> <li>Netlaunch can now start disabled.</li> <li>Netlaunch can now launch just about anything in the Launch List. In order to do this, I had to make some changes to the way it stores program launch preferences in the registry. THIS MEANS YOU HAVE TO RECONFIGURE YOUR PROGRAMS IN NETLAUNCH. Sorry, but the feature was worth the inconvenience...at least *I* thought so...</li> <li>Changed the way it waits for the Reconnect dialog to appear--this should fix everyone having problems with Netlaunch not reconnecting on disconnect.</li> <li>Added minimum connection speed checking, so Netlaunch will disconnect and redial if the minimum connect speed is not met.</li> <li>Fixed a problem with retrying a connection if you are using MSDUN1.1 or above and had the "Prompt for information before dialing" un-checked in the DUN settings.</li> <li>Some minor internal changes in preparation for beta testing to begin on NetLaunch version 4.0</li> <li>Added hyperlinks to the About Box so people could send me e-mail and go to my webpage easily.</li> <li>Moved the Schedules to memory, so Netlaunch no longer bothers the registry every second.</li> <li>An improved Idle Disconnect. Microsoft relies on the modem's "S-Registers" to drop the connection after it's been idle, but often the modem either doesn't use it, or will maintain the connection because of intermittant usage. Netlaunch can now check the percentage of use, and can disconnect the modem when it's really idle, or when the usage drops to a user-defined percentage over a user-defined period of time.</li> <li>The context menu now appears quicker, especially in NT4/NT5.</li> <li>Added sub-directory support for the Launch List. Now you can have submenus within the context menu!</li> <li>Created my own custom self-extracting executable installer/uninstaller. I got tired of dealing with the Windows Setup API DLL's and that INF file I was using before.</li> <li>Added several files to the archive, including the NLUNLOAD.EXE program. This program can unload NetLaunch, and I've had many requests for it. You can even put this file in the Launch List and have NetLaunch run it.</li> </ul> <hr> <big>3.13a</big> <ul> <li>Fixed the "Disconnect after connected for xx" scheduled event. It was disconnecting after a minute regardless of the setting.</li> </ul> <hr> <big>3.13</big> <ul> <li>Added PIF file support for launching MS-DOS programs and batch files. NetLaunch cannot close down or sense the closing of DOS programs, but it can at least launch them for you now.</li> </ul> <hr> <big>3.12</big> <ul> <li>Up to this version, NetLaunch was getting the verbage for the "Connect to" dialog from the dialog box in RASAPI32.DLL in Windows 95. What I have come to find out is that Windows 95 uses the "Connect to" stringtable entry to give that dialog box its title, and ignores the original dialog box resource's default title. The Brazilian-Portuguese version of Windows 95 has a slight discrepancy that caused this to become an issue. The dialog box title said "Connectar A" and the stringtable entry said "Connectar a" ... so NetLaunch was not pressing the button because it was looking for a capital A and not a lowercase A. This may also fix some problems NetLaunch was having with the Japanese/Chinese versions of Windows 95.</li> </ul> <hr> <big>3.11</big> <ul> <li>NetLaunch now expands error dialogs that cannot fit the "retry" and "cancel" buttons, so that they will fit.</li> <li>No longer repeatedly minimizes the "Connected to" dialog over and over. It only does it once now.</li> <li>Fixed a menu bug in the left-clicked menu that would cause the menu option not to be activated when clicked if the default ISP connection was set to not show in the context menu. The right-clicked menu was unaffected.</li> </ul> <hr> <big>3.10</big> <ul> <li>Fixed a problem with connections scheduled to begin on startup. Sometimes it was opening several connection windows and trying to connect.</li> <li>For programs set to close "just prior to" a connect/disconnect, NetLaunch will now wait until the program is completely closed before continuing. This could cause an infinite loop if the program does not close after NetLaunch tells it to. Closing the program manually is the only way to make NetLaunch continue after that.</li> <li>Added full support for the NetLaunch API! The API is completely finished, but as of May 9, 1997 I have not completed the API documentation. Contact me or keep checking my webpage for availablility. It will be available free of charge for anyone who wants it.</li> </ul> <hr> <big>3.10 Beta 5</big> <ul> <li>Fixed a GP fault with manually-launched programs (this was actually fixed in a second upload of beta 4, so you may not have seen this error)</li> <li>Slight alterations to the helpfile & the Program Prefs dialog to make room for future additions.</li> <li>Added a very tiny .WAV file player (PLAYWAV.EXE) to the archive. This will let you play any .WAV file on a connect/disconnect event. It gets installed to your WINDOWS directory along with NetLaunch.</li> </ul> <hr> <big>3.10 Beta 4</big> <ul> <li>Broke the scheduler in beta 3. Fixed! Sorry.</li> <li>Fixed a reconnect bug. NetLaunch was minimizing the "Connected to" dialog when it appears underneath the "Reconnect/Cancel" dialog, and it should not have been. It was causing all sorts of problems.</li> </ul> <hr> <big>3.10 Beta 3</big> <ul> <li>Fixed the left-clicked menu problem when you've selectively hidden DUN connections. It would either not launch the connection or would launch the wrong one.</li> <li>Added minimize Internet News & Mail to the software. It now will check if it is launching Explorer, and will adjust its method of minimizing the application accordingly. To auto-minimize either Internet News or Mail, open the Launch List, right-click on the icon, and select Properties. Select the Shortcut tab, and change the run mode to "Run minimized". NetLaunch will take care of the rest.</li> <li>Added no-focus launching, so apps can be started without giving them the window focus. This doesn't work for all apps, only those written properly. (Internet News & Mail do not pay attention to the NoFocus param...losers!)</li> <li>Altered the GUI behavior for the Launch Options. You may now select the "Only one instance" and "No focus" checkboxes for manually launched applications.</li> </ul> <hr> <big>3.10 Beta 2</big> <ul> <li>Added "just prior to" options for launching/closing programs prior to a connect or disconnect</li> <li>Fixed the context menu bug introduced in beta 1</li> </ul> <hr> <big>3.10 Beta 1</big> Added a lot of new features! Things like: <ul> <li>Retry on error like Windows NT...this is WAY cool!</li> <li>Can now press either "Reconnect" or CANCEL on a DUN disconnect</li> <li>Can minimize or hide the "Connected to" dialog</li> <li>Can prevent program icons and connection icons from showing up in the context menu</li> </ul> Fixed some of the problems preventing me from enabling all the compiler optimizations, so now the program is even smaller than it was before! <hr> <big>3.06c</big> <ul> <li>Fix for Spanish version of Windows 95. Seems there was a trailing space on the "Connectar Con" string in the RASPI32.DLL which is trimmed when the window is opened, and NetLaunch was unable to "see" the window.</li> <li>Fixed an unhandled exception error when disconnecting from an ISP in Windows NT.</li> </ul> <hr> <big>3.06b</big> <ul> <li>Added disable support. NetLaunch can now be enabled and disabled</li> </ul> <hr> <big>3.06a</big> <ul> <li>Fixed a small GUI bug</li> </ul> <hr> <big>3.06</big> <ul> <li>More tweaking on the GUI, specifically the Launch List launch and close settings for programs.</li> <li>Fixed the Destroy Window. It was not working at all.</li> <li>Changed the methodology of how NetLaunch looks for windows to send close or destroy messages to. Previously, NetLaunch would simply enumerate the windows of the main thread of an application. However, this was not working on many programs that create windows in spawned threads (other than the primary thread). NetLaunch now enumerates all the windows and matches them with their Process ID's to determine which apps own which windows. It can now send messages to windows no matter which thread of an app opened it.</li> </ul> <hr> <big>3.05d</big> <ul> <li>Fixed an unhandled exception in NT when dealing with the context menu change I put into 3.05c (grin)</li> <li>Added a new checkbox to remove the connection entries from the context menu when you are already connected.</li> </ul> <hr> <big>3.05c</big> <ul> <li>Changed the context menu to handle huge amounts of programs in the Launch List. Previously if you were in 640x480 and had a lot of programs in the list, the menu would keep going down vertically, even past the end of the visible display area. Added logic to allow it to do multiple columns.</li> </ul> <hr> <big>3.05b</big> <ul> <li>When I reworked the disconnection detection code for NT a while back, I accidentally broke the "press redial button" code. FIXED!</li> <li>Fixed a very tiny GUI bug when you've added a new connection to DUN. It would sometimes show the "Apply" button when you hadn't changed anything in the "Connections" tab.</li> </ul> <hr> <big>3.05a</big> <ul> <li>Removed "push buttons for all dialup connections". It is now automatic and can not be disabled. Most of the "dialog skipping" routines required this feature enabled and would not work otherwise.</li> <li>Fixed long dial-up names. If the name of the dialup connection is longer than 18 characters, Windows95 truncates the name and appends "..." to it. This was throwing off NetLaunch, especially since the behavior in OSR2 is different than old Windows 95.</li> </ul> <hr> <big>3.05</big> <ul> <li>Small tweaks. Fixed a couple small bugs when trying to press buttons for the "Connect To" dialog.</li> <li>Messing with the optimization settings for my compiler. Some of the features are causing inconsistencies between my debug and release builds and are causing a lot of problems. Unfortunately it means the executable is a little bigger now.</li> <li>I was leaving some handles open when it launched/closed programs. Fixed!</li> <li>The Launch List in the Preferences screen is updated properly when you chang the Launch List directory. You no longer have to exit Prefs and come back in</li> <li>Changed the way I resolve links and ask for a pathname/filename from the system. I was asking for the shortpath (8.3 format) instead of the UNC path, and some programs...well, ONE program didn't like it. It was Agent 1.0.</li> <li>Separated the INF file into two versions, one for NT and one for 95. Why can't Microsoft name their setup API DLL's the same in NT and 95? It'd make the uninstall process SO much easier!</li> <li>Fixed the "Hide connected dialog" button...was not updating properly</li> <li>Fixed a long ISP name bug...The "Connect To" dialog was truncating the name in the static control I was looking at--fortunately there's a hidden on in the dialog with the full name.</li> </ul> <hr> <big>3.04</big> <ul> <li>Fixed a major bug that could cause your system to get seriously unstable after running NetLaunch for a long time. I kept opening the registry key every 2 seconds and not closing it...so each time it would open another handle, then another, then another...you get the point. I didn't catch it until I ran NT's task manager. (Thank God!)</li> <li>Fixed a small registry cleanup bug</li> <li>Added a time-delay launch so a program can launch after a designated period of time after a connect. That way it doesn't totally cripple your system by launching all the programs at the same time.</li> <li>Can now hide the "Connected" dialog...None of this minimizing crap. It's GONE! (I always hated having that window in my taskbar!)</li> <li>Added left-click support and a new "Connections" hotkey. Left-clicking on the NetLaunch icon now brings up an abbreviated Connections menu, allowing you to connect and disconnect. The hotkey does the same thing, only with the keyboard of course.</li> </ul> <hr> <big>3.03</big> <ul> <li>Fixed a bug when executing command-line params that caused programs to be launched in the Launch List.</li> <li>The program now reports when it cannot resolve a link.</li> <li>NetLaunch can press the "Connect" button and override username/password in NT. Of course, this only works if the dialog pops up.</li> </ul> <hr> <big>3.02</big> <ul> <li>Fixed the fix to scheduling</li> <li>Fixed disconnect detect problem in NT</li> <li>Will no longer try to connect to a connection already established</li> </ul> <hr> <big>3.01</big> <ul> <li>Fixed the Windows NT support. It was WAAAY broken. (I had to install NT to do this however...sigh)</li> <li>Fixed the Launch List directory defaults...it was broke, too.</li> <li>Fixed the scheduling bug for connections with an underscore.</li> <li>Fixed numerous incorrect registry access functions that NT is more picky than 95 about.</li> </ul> <hr> <big>3.00 Released 04-25-1997</big> <ul> <li>Fixes from the most recent beta:</li> <li>Fixed a dumb (but elusive) bug that erased the "program" tab preferences when you were in the Launch Opts screen (and had not switched to "Prog opts") and changed one of the "Apply to all/each" radio buttons. Duhh!</li> <li>Made the Prefs screen a little smarter. It doesn't give you the "Apply" button now unless you really CHANGE something.</li> <li>Removed the multimedia timer I was using for scheduling, and made the schedule timing code smarter so it didn't require the kind of accuracy I needed before.</li> <li>Fixed a bug that caused the helpfile to be repeatedly shown when you had no items in the Launch List. Oops!</li> <li>It now disables the functions that do not work on Windows NT, namely the button-pressing options.</li> <li>Small cosmetic changes. Fixed incorrect tab orders, fixed a font bug that caused the entries in the context menu not to reflect the current menu font if you changed it while NetLaunch was running. Centered text and icons in my owner-draw stuff so it looks better with non-standard fonts and sizes.</li> <li>Added some more information about the "Only one instance" checkbox and its limitations in the current release.</li> <li>NetLaunch tries to put your default Dial-Up connection first in its menu, but it sometimes put a bogus name there if you changed the name of your connection but had not used it yet.</li> <li>Put the LAUNCH.INF back in the ZIP file. Oops!</li> </ul> </body> </html>