soporific

OK, you need to provide much more information than that. What did you try that is not working?

i dunno if this is the best forum for your question but here's some examples of the code i use for some of my scripts: Run("kb931836.exe /Q:A /R:N") WinWaitActive("Date/Time Properties", "") Sleep(1500) ControlClick ("Date/Time Properties", "", 1) and <beginning snipped> ControlClick ("Finished", "", 1023) Sleep(999) ControlClick ("Finished", "", 1024) Sleep(999) ControlClick ("Finished", "", 1) Notice how they both use the exact information as opposed to just sending a return key. If you use the information tool that comes with AutoIT 3.2 it will tell you the text you need to look for. You need to get the text EXACTLY right otherwise the active window won't be found. Then use ControlClick with the same info to exit. So, use the tool to find the exact text of the dialog box, and also the ControlID of the control you wish to click. And then use the example above to exit the last box. HTH

Latest News: v1.96.58 is out get it here: upgrade 1.96.50 to 1.96.58 file size: 297kb changes from 1.96.57 to 1.96.58: 1) there is a big code bug in 1.96.57 that may or may not trigger. It doesn't seem to be a problem in normal program operation - the bug is in the code for the menus at the start of the program so its nothing important, but a very common label has somehow been repeated twice and its only because the proper one is above the wrong one that nothing appears different. 2) If you try to exit the program with CTRL-C (like the screen says at the end), AND you have rebooted at least once during the patch session, when you exit you get another DOS window with a message saying "Batch file missing". This file is supposed to be missing, you just aren't supposed to see that message. EDIT: the suspense is killing me ... is this version any good? The new May 2007 is all ready to go but i want at least one word of feedback on the new code before releasing! So i hereby announce a competition: the first person who replies with some feedback about 1.96.57 or 1.96.58 will be awarded: 10 points, a commendation from the God of Feedback, good luck for a week, a gold star, a plaque commemorating this achievement, a purple flower stamp, and some Che Guevara Lip Balm. Ok so i'm lying about the plaque and the lip balm, but the rest is all waiting to be won ... OK, wait for it .... Ready ..... Steady .................. GO! EDIT2: - Yes!! my dastardly plan seems to be working perfectly!! ... you see, the reason no-one has given any feedback is because the code was written in such a way as to make all those who install it and use it, completely disappear! Yes, that's right, Auto-Patcher is actually a disintegrator in disguise, and i actually work for Microsoft who want me to bump off everyone still using Windows 98. It's working!! If you think i'm joking, why not try installing it yourself... you could always come back and tell me i'm wrong ... and while you're here you may as well say something about the program itself ..... edit3: and the winner is .... LL028!! ... now about that gold star and purple flower ... just give me a sec ...

Okay, done it. No Win98SE programme upgrades (early days?). What it seems to have done is tacked another line i.e.SHELL=COMMAND.COM /E:4096 /Pinto CONFIG.SYS in C:\ , didn't touch the CONFIG.SYS in C:\WINDOWS\ (which I don't think should be there in WINDOWS anyway). Slight EXPLORER error message whilst installing. A file called CONFIG.SYZ seems to have appeared in C:\ ... anything to do with AutoPatcher98? I've never heard of SYZ files before. Keep up the good work! 1) if you have CONFIG.SYS in C:\ it is in the right spot. If you have one in C:\Windows you don't need it. 2) CONFIG.SYS gets backed up to CONFIG.SYZ when you install the fix. I choose that ending because i wanted it to be unique. Other programs use CONFIG.BAK so i didn't. It isn't an error message, its just telling you what its doing. 3) Does it all seem to work? EDIT: - i've noticed a hung DOS windows while testing out 1.96.57, it happens after the first run thru the VB runtimes module, it hangs when trying to reboot --- this shouldn't actually be a code bug, the problem is actually the last update in the module. This is a known bug and has already been fixed in the upcoming version. EDIT2: -- um, er, there is a big code bug in 1.96.57 that may or may not trigger. It doesn't seem to be a problem, but it seems i'll be releasing 1.96.58 after all. Stay tuned ... the bug refers to the menus at the start of the program so its nothing important, but a very common label has somehow been repeated twice and its only because the proper one is above the wrong one that nothing appears different. But for forms sake, and to also fix the wrong report of a missing batch file, here's an updated version: v1.96.58

OK, there's a little thing i should comment on so you aren't concerned. If you try to exit the program with CTRL-C (like the screen says at the end), AND you have rebooted at least once during the patch session, when you exit you get another DOS windows with a message saying "Batch file missing". This file is supposed to be missing, you just aren't supposed to see that message. This isn't worth releasing another version over, but i will definitely fix for the next version.

OK, the new release is just about ready, so it will be added to this post within the hour. Please install it ASAP and test it. If everyone says its good, we go to the next release immediately. It looong overdue. You will need to have 1.95 PR2 & the 1.96.50 upgrade already installed. Which most of you have. If you have any of the dud fixes (1.96.51-1.96.55) just install this over it. Coming soon ... EDIT1: just for those curious, this is the AUTOEXEC.BAT file i was testing the new version out on. Check out the length of the PATH statement. Don't forget to notice that there is another string tacked on (the line with DiskeeperLite), the resulting PATH statement is 279 characters long (it was breaking at 137). And add that to the other SET statements, the resulting use is 383 characters. And it runs no sweat. This is not the limit, it's just what definitely works. I'm sure i could squeeze more space, but who know's what system the user has so this will do. So, ..... I NOW DEFY ANYONE TO BREAK THE LIMIT! Go on, install as many programs as you wish that all just have to install their path into the global PATH statement, AP will take it all and not even blink. Coming soon ... SET BLASTER=A260 I9 D3 H3 T4 @rem - By Windows Setup - For 1st Boot - C:\PROGRA~1\COMMON~1\NETWOR~1\VIRUSS~1\40~1.XX\scanpm.exe c:\ @IF ERRORLEVEL 1 PAUSE SET PATH=%PATH%;c:\progra~1\common~1\gtk\2.0\bin\HereBeAnAwfullyLongPath\ HereBeAnAwfullyLongPath\HereBeAnAwfullyLongPath\HereBeAnAwfullyLongPath\ HereBeAnAwfullyLongPath\HereBeAnAwfullyLongPath\OkThatsAll SET Path=%Path%;"C:\Program Files\Executive Software\DiskeeperLite\" SET OGRE_HOME=c:\OgreSDK SET CLASSPATH=.;C:\PROGRA~1\ARTOFI~1\LIB\SOUND.JAR;C:\PROGRA~1\ARTOFI~1\LIB;C:\PROGRA~1\ARTOFI~1\LIB\JMF.JAR EDIT2 I split the PATH statement into 3 because it was screwing up the thread. And there's a little hiccup that's proving not easy to fix. Sorry... hoping to crack it... will report back soon ... EDIT3: OK it was a false alarm, i'm still releasing before i hit the sack. I soo want to get it out i was horrified when i saw hung DOS windows ... all fixed now. EDIT4: i nearly forgot to add the ES fix as an menu option just in case you pass the ES test but still have problems later on. Everyone, if you even had ONE problem with an 'Out of environment space' problem of some sort, please visit the full main menu and visit the fix option. You will definitely spot it. trust me. Coming soon! EDIT5: i may as well add instructions now ... OK this is the way i've gone with. People who have a reasonably long PATH statement (but not too long or ridiculous) will fail the Environment Space (ES) test on purpose. This is because they are likely to have problems if they don't install the fix and i want to trap them at the start. SO be prepared for this and don't freak out when you fail. Install the fix, reboot, restart AP and you should be fine to go and do what you want with it. If you still see errors, please report as soon as possible. If you want to be sure, you can visit the main menu and install the fix even if you don't fail the test. More information is available from the option. If you need more help, just ask. EDIT6: v1.96.57 is out get it here: upgrade 1.96.50 to 1.96.57 297kb Please read EDIT5 for the instructions. Please report bugs ASAP. This release is safe to install, just please read all instructions. EDIT7: - if you've just joined the discussion... it must be a bit confusing to say the least ... only recently, as the program has been getting bigger, some people have been reporting problems with their environment space. And the program starts to behave erratically. So the newest version should finally fix all these problems. If you've just joined us and want to install everything, this is what you need: Auto-Patcher v1.95 Preview Release 2: (use the first link please, only use the others if the first doesn't work) http://soporific.files-upload.com/135464/A..._insta.exe.html download.com softpedia http://soporific.dsleague.com/downloads/Au...2_installer.exe - file size: 241 MB Auto-Patcher v1.96.50 Upgrade: upgrade 1.95 PR2 to 1.96.50 - requires v1.95 PR2 already installed - file size: 17 MB Auto-Patcher v1.96.57: upgrade 1.96.50 to 1.96.57 - requires v1.96.50 already installed - file size: 297 KB Also, please read the first post for more info about the project. Cheers! And don't be afraid to say something. OK, i think i'm going to retire for the night. Cheerio.

I'm glad you like reading them, because i like writing them, especially the good news ... NEWS: OK, up until now the environment space (ES) problems were still coming up. I am using a version of Jack's (Nathanson1947) autoexec.bat file as a test, but i've made the PATH statements even longer so i can try to fix this problem in all scenarios. My first task of the last couple of days was to get the bat files under control (ie be totally clear on what they are doing). This is now done. So the next thing i did was create a better debug system that shows me what the system is doing at each stage, with reference to variables. I outputted the complete SET (pun intended) of variables to check they were all needed all of the time. ...... ..... ..... my goodness. Talk about making life hard for myself. I was able to reduce the number by about a third !! Needless to say, i'm having less ES problems (i have to increase the PATH statement in AUTOEXEC.BAT to create an error). That's good news i think! EDIT: Far ............. out ............. you know, you can stare at code for long enough to not be able to see the forest for the trees. So the program is running fine, except it keeps exiting out at the DirectX module ... and when i REM out all the PATH statements in AUTOEXEC.BAT it works perfectly. So you would assume it's an ES problem wouldn't you? Nooooo ... i still had a COMMAND /E:2048 instead of %COMSPEC% /E:2048 at the end of the file and for some reason this would NOT work under low ES conditions and works fine with lots of space. ??? Grrr..... EDIT2: sorry about the last edit, it looked really negative and suggested things weren't going well. They are it's just that in some circumstances (ie those with jam packed AUTOEXEC.BAT files), the ES problem returns. I've been experimenting with various fixes and the one that is the best is to give the user's system a higher default environment space for each session of the command line interpreter (ie each DOS box session). It just wipes out all the problems with one simple addition to the user's CONFIG.SYS - then, you can have the longest PATH statement in the world and AP won't even blink. In fact AP will be sooo happy with all the extra space to play in, i don't expect a peep out of the little feller for any reason other than total meltdown. So, all i'm doing now is devising a stand-alone CONFIG.SYS fixer and then its release time. What's coming is the update to fix the problems associated with the upgrade to 1.96.50 --- but all those who were still trying to survive on 1.95 PR2 (because 1.96.50 didn't work) should upgrade immediately. For all those who never had any problems, you may as well stick with 1.96.50. The new upcoming full version release already has the fixes written (they were tested on the new version first actually) and is coming very soon ...

Yes, yes you do. You may find this funny ... a bug i just fixed then: I have a function called NiceTime that converts a 6 digit time into something less specific .. ie a nice time. Anyway, it rounds the seconds either up or down depending if its under or over 30. And i left it at that. So just then i started a report at 1:59:46 and this gave me the very normal looking time of 1:60pm ... the chance of that happening is 1 in 120 if my math serves me correctly. Has now been fixed.

NEWS: hoh boy, the new version rocks. No more DOS windows dancing around the screen!! I've never been able to compare the two methods before and i must say i like the screen staying where it is the entire time. It doesn't move once! I've finally got some semblance of control over my pet bat files, naughty little buggers they are. Run-Mod.bat has been fired and shown the door. Totally surplus to requirements. And Fullup.bat, always the odd one out in the modules folder (its not a modules file), has been moved up a directory level where it always should have been, and renamed ModMenu.bat The other improvement is the report function now reports more missing updates. It wasn't counting the ones that you couldn't install because other things were missing. It is usually only a few updates so its easy to miss. It will mean some of your figures of what is actually missing compared to what the report says, will now make sense. Hopefully. So thanks for all the most recent posts, the new version is much better as a result. It will be out soon ...

Yes, they are. Let me explain. Rather than just use the filename for the 'short title' of the update, i've gone with using the Q number or the KB number (numbers before 400,000 are Q and ones over 800,000 are KB). SO you WILL find 237493usa8 if you search for 237493 (which brings up q237493) and hover your mouse over the download link. Same with 249973USA8. i agree and i will add as i come across them.Edit: you could ease up in the script code with the filename. As long as the entire number is found in the filename, then the update exists, rather than restricting to the original name. We would then be in harmony.

That's a mighty fine list you have there ... once in a while i get feedback worth a ton of gold ... and this is one of them. Thanks to you !! I'll be slowly working my way thru the list in the next few days ... lots will be added to both the main list and obsolete list i have no doubt. Thanks again! EDIT: i take it all back !!!! Well, i'm not taking back the thanks for the thought to tell me about these missing updates, but my initial check of the first few items on the list was like: where are the missing ones? ie of the following, most are already in the list! And a quick scan down the list says there's many more! So, my question before i continue down the list is how did you come up with this list? Of the first 9, about half are obviously already there ... it just doesn't make sense! Please advise !! (and for some light relief humour, lets remember another celebrated occasion when 'it doesn't make sense!' -- this is one of the best South Park sequences ever, it even has its own wiki page - http://en.wikipedia.org/wiki/Chewbacca_defense "Cochran: Ladies and gentlemen of this supposed jury, Chef's attorney would certainly want you to believe that his client wrote "Stinky Britches" ten years ago. And they make a good case. Hell, I almost felt pity myself! But, ladies and gentlemen of this supposed jury, I have one final thing I want you to consider. Ladies and gentlemen, this is Chewbacca. Chewbacca is a Wookiee from the planet Kashyyyk. But Chewbacca lives on the planet Endor. Now think about it; that does not make sense! Gerald Broflovski: Dam* it! Chef: What? Broflovski: He's using the Chewbacca Defense! Cochran: Why would a Wookiee, an eight-foot tall Wookiee, want to live on Endor, with a bunch of two-foot tall Ewoks? That does not make sense! But more important, you have to ask yourself: What does this have to do with this case? Nothing. Ladies and gentlemen, it has nothing to do with this case! It does not make sense! Look at me. I'm a lawyer defending a major record company, and I'm talkin' about Chewbacca! Does that make sense? Ladies and gentlemen, I am not making any sense! None of this makes sense! And so you have to remember, when you're in that jury room deliberatin' and conjugatin' the Emancipation Proclamation, [approaches and softens] does it make sense? No! Ladies and gentlemen of this supposed jury, it does not make sense! If Chewbacca lives on Endor, you must acquit! The defense rests.") Gotta love South Park ...

Thanks for your comments, don't worry i have already taken a little break, i haven't touched the code for a full day ... towards the end there i was going totally stir crazy -- my 'builds' were getting progressively worse ... i've actually worked out where and when all the problems started ... i was using %COMSPEC% /C in all places and only recently changed some of them to %COMSPEC% /K but Mazabuka and yourself have correctly pointed out i should have been using CALL instead. I will return to this tomorrow and hopefully a version soon ... thanks again for the words of encouragement. EDIT: i meant to say 'changed to %COMSPEC% /K' in the post above (i have made the change)

That's excellent investigation ... i was trying lots of things all over the place without pausing to think it through ... eg clearing the variables before running the next bat file ... as you noticed i only recently did that to try to solve the problems. I never did quite get a complete handle on everything to do with environment space (ES) so this post is a wealth of information. I completely buggered up my current version of code last night as i was trying to fix this problem so i'm going to totally junk last nights work and start again using the above info. Maybe another version later today... PS - please trim your posts a little before posting. --- and these are some useful tags to use: [ quote ] & [ /quote ] and [ code ] & [ /code ] but without the spaces. eg example using "code" it helps navigation and readability! Thanks again for such an awesome post!

what is it with people and their humungous PATH statements in their AUTOEXEC.BAT files ? No offense Plonk me mate ... OK this advice is the definite way to temporarily solve most AP problems where it just exits out ungracefully. If the following is true: 1) When you use AP, especially the 1.96 upgrade, it doesn't reach the end, or it doesn't even start, or you see "Out of environment space" messages. 2) Inside your AUTOEXEC.BAT file you have a "SET PATH= ...." or "SET CLASSPATH= ..." that is quite a long string of text. You can by-pass this problem by doing the following: 1) go to START - RUN and in the Run dialog box type SYSEDIT and hit return (enter) -- this brings up all your configuration files into like notepad type windows 2) choose the AUTOEXEC.BAT window, and any line that starts with "SET PATH= ...." or "SET CLASSPATH= ..." put the word "REM" at the start of the line. eg if your AUTOEXEC.BAT looks like the following: you would then add REM words like this: you don't have to REM out all the lines, just do the really big one that is causing all the fuss !! After you use AP, just return your AUTOEXEC.BAT file to the way it was by taking out the REMs. What is the effect of adding REMs? What will happen? You were wondering weren't you... it just means that the particular program that 'installed' that PATH statement (or whichever variable it is) won't be able to run normally while that REM word is there. SO this means that if a anti-virus program has added a line then maybe keep that unREMmed. Again, the easiest thing is just to REM out one line --- which line? The longest line! That's right, you there at the back. I am writing a function that will do this as a menu option and or if you fail the ES test but until then, everybody in this situation, this is what you do!

Jack, glad to be of help. Re: v1.96.55 i know why it doesn't work ... i'm just testing out the ultimate ES error proof version now ... its way cool !! Back soon ...

I know i know, but you know how users can be, they like playing around and sometimes will try installing something twice because they didn't think it worked the first time, etc. So i just try to avoid the user being able to make this mistake. If we can't avoid it then thems the breaks. I'm not too fussed about the method we use, if we need to use a DOS batch file, thats what we use. That's the way i've gone with ... i've already re-done the hotfix to overwrite without asking questions, and i've made the hotfix optional inside AP with an explanation that tells all about what's going to happen. Great minds think alike! If you make another installer for Q891711 i will use yours instead. Thanks for all your help as usual.

jeepers. can you do the same as nathanson1947 and run SYSEDIT from the run dialog box and post me the text inside AUTOEXEC.BAT (post as a PM). Thanks. NEWS: it seems i still have some work to do to solve these ES errors. I didn't have much time to test 1.96.55 out last night and its still bringing up errors. Even Just trying to set DEBUG=Y inside START_ME.bat brings up an ES message - I have to trap the Out of environment space messages everywhere, and not just where i have so far. So please bear with me. Please only install the latest updates if you want to help solve these ES problems. OK, the main problem is now this: if the user has used up all of the normal ES space, unless the first file (START_ME.bat) is started with its own space allocation, there is no more space to assign the necessary variables for the program to work normally. Using nathanson1947's AUTOEXEC.BAT file (with some very long PATH statements) the program can't even set DEBUG=N and so things immediately stuff up. The entire point of START_ME.bat was to give enough space to AUTOPACH.bat so all the variables would be set properly. Now the problem is I have to do this for START_ME.bat which is going to be tricky. That or i just save the path statement to a text file and reset it for the autopatch session and then reassign it at the end. Yep, i''l try that out first ... back soon ... Well, it works ... so this is now what happens: START_ME.bat is started and it tries to assign DEBUG=N --- the very next line it tries to find that variable and if fails, goes to the fix section. Your PATH statement is reset to the bare minimum (ie SET PATH=%windir%\command) and then the process is tried again. If you fail twice you get a message and are invited to quit. It seems to work! But i'm testing some more before posting ... EDIT: its looking good ... -- i'm quite proud of this fix actually. It doesn't matter what sort of system you throw at me, my AP will work if its the last thing i ever do !!

far out. i just can't win. OK, what you need to do is send me the actual text of the contents of the AutoExec.bat file. I want to know just how long those path statements are ... i was so sure this was the last one.... just PM me ... no need to tell the world what you have ... EDIT: great news: I am replicating your problem right in front of my eyes.. so there's no more stabbing in the dark. bad news: well, it seems your autoexec.bat file is screwed up. I'll suggest the changes soon, but do something for me can you. Reboot your machine, and when its rebooting, if you have your boot logo still turned on, press ESC to see the boot messages, and tell me if you see the following: notice the "too many parameters" message did you get that on your machine? If not, please double-check the text of the autoexc.bat file you sent ... cheers. EDIT 2: i can see the problem in AP. There is a command to run Run-Mod.bat with no extra space allocated at all. It didn't matter until the path of the program location was long enough to trip the ES warning on systems that were using lots of ES space to start with. Wow, i've just made the adjustments, and it all works. This was a bona fide bug !! The next version is the winner! Coming soon ... here it is: http://soporific.dsleague.com/downloads/Au...6.55_update.exe by the way, you still had a problem with your Autoexec.bat file ... the reason is due to the order of installation .. the fix is to move the entire line with diskeeper lite in it below the one with gtk in it. When you reboot, you will see there's no parameter error. The reason is due to the long path name for diskeeper. As you can see, it is added to your path statement fine, but when some more text is added to the path the second time the diskeeper path is missing the quotes, hence the errors. IF you swap them around, this problem doesn't appear.

Excellent! We have worked out what was wrong and I suspect others are in the same boat. So, it looks like i'm upping the space allocation. nathanson, we haven't finished yet. We want to get it working without you REMming stuff out but i think i know what is going to work. Back soon ... EDIT: Ok the next version will have 2 changes: * the space allocation has been doubled in 2 places - START_ME.bat and RUN-MOD.bat which are the 2 files that dole out the memory. grab it here: http://soporific.dsleague.com/downloads/Au...update.exe file size: 227kb you must have v1.96.50 already installed. If you have v1.96.51, v1.96.52, or v1.96.53 installed, its fine to simply install the newer version over the old one.

Nah, its much easier than having to employ your BASIC skills, it really is dead easy otherwise i wouldn't have suggested it ... when you use SYSEDIT to bring up your configuration files, they are loaded into a notpad style window which you can edit. If you want to make a back-up first, just open notepad, navigate to the root of the c: drive, make sure you select all file types, and you should be able to open AUTOEXEC.BAT and then save a copy as you would a normal text file. REMming out a line simply means putting REM at the start of the line ... i added the two dashes just for aesthetic reasons. Don't think of the AUTOEXEC.BAT file as anything else other than a text file with some text inside it. But if you needed to make a backup of your autoexec.bat file i would have said. REMming out your PATH statements simply means you can't use those programs until you put them back in. Just use SYSEDIT to adjust your file. Reboot. Test AP. Use SYSEDIT again to unREM the lines. and reboot. Your computer is back to normal.

well, i was right !!! ... it seems ... i shouldn't get too excited as i've only tested on one piece of hardware, but the method seems sound. The INF file for my hardware wasn't very silent and so i had to click thru stuff, but the point was the computer did the following: 1) it found an unknown piece of hardware 2) it found an INF file for it. 3) and i forced the process above and am able to automate it. it seems the rest of the task is easy ... unfortunately most if not all INFs will have to be modified to be nice and silent but maybe it won't be so bad ... my plan is that the Driver Pack will simply have the drivers i have a need for and the INFs for those will be done by me. If you want to include your drivers, you are going to have a much better chance of getting them *quickly* inserted by doing the modding of the INFs yourself. I only recently learnt myself its not that hard. SO now i'm working on a method to use the driver packs *whenever* -- ie we don't want to just use it when re-installing the OS ... what about if you come across a piece of hardware and you had *no* idea what it was, theoretically, if the driver packs were big enough, all you would have to do is run them and the hardware would be installed. There's no hope that this project will ever get to that stage but the concept would be interesting to nail down ... i can think of many uses for a universal automated driver installer. SO if i release something, you should be able to test it by creating your own test driver pack (simply an archive of the needed files) and checking it out ... that's the plan ... back soon ...

no the report text is normal for a session that exits out ungracefully. ... Nathan my son, the fix was always only a stop gap, it doesn't help us explain what's going on with your system. If you could do that REMming out in your AUTOEXEC.BAT file as i described in the previous post that would actually help us determine one way or they other. This stabbing in the dark is quite time consuming for us both. Although. i should have just lashed out and given you an extra 2048 bytes of space instead of a measly 1024 and the taking out of the breakpoints was a bit premature! So i'll do another one but only after you report back how you went with the REM stuff. Ask if you need more clarification ... Edit: 'Senior' sooooooo gives the wrong impression about me

MDGX: thanks for that info. i've been doing some testing and it appears that if the user attempts to install the Q891711 update twice and doesn't uninstall in between then their system is stuffed when they reboot. User.exe and User32.dll are missing and the only ones on the system are the backed up ones (ie USER.O98 and USER32.O98) ... is this a known issue? And there's another issue --- what if a user has Windows 98-2-ME installed? Like the full super duper version with the v5.50 files? Will the user's system function normally? I could test myself but maybe you already know ...

Ah ha! It IS due to environment space! Notice the 'Out of environment space' messages .... i will attempt to overcome this by allocating more space for the processes. New version will be available soon ... EDIT: i think i can see the problem -- you have your AUTOEXEC.BAT file adding very long strings to the PATH and CLASS PATH variables. To check if this is the case, adjust your AUTOEXEC.BAT file to REM out each line that starts with SET ie SET PATH=(blah blah blah) SET CLASSPATH=(blah blah blah) becomes REM -- SET PATH=(blah blah blah) REM -- SET CLASSPATH = (blah blah blah) (only the REM word is important) then reboot your computer and see if AP works without errors. After we have determined if this is the problem, you can un REM the lines to return to the original state. Regarding the point where no keys would work, this is probably due to the ES problem but i must admit i've never come across that particular issue. New version: changes from v1.96.52 to v1.96.53: * the ES test is slightly harder to pass - its now back to the test version inside v196.51. * the breakpoints have been removed * the space allocation has been increased by 1024 --- this should solve the problems. grab it here: http://soporific.dsleague.com/downloads/Au...update.exe file size: 227kb you MUST have v1.96.50 already installed. If you have v1.96.51 or v1.96.52 installed, its fine to simply install the newer version over the old one. EDIT 3: can someone say something so i can reply ... i want to post my 500th message! ..... not that i'm counting or anything ... and it's not because i want to "level up" which is what's going to happen at 500. Really, truly! edit 4: i suppose i could just cheat ...

here's 3 screenshots about 'Improving Readability' the first shot was buried in the help section for 1.96.50 so here it is in case you've never seen it: +++ +++ The choice is pretty clear from where i'm sitting. Make the change today! - you will need to change the setting from Auto to your desired setting 2 or 3 times (for different files that are used) but your computer will remember your choices for future uses. It is HIGHLY RECOMMENDED to spend the required 30 seconds playing around with all the options to get the optimal setting.