Skip navigation
This discussion is locked

11.1.102.62 and Win2K install - SetDllDirectoryW not supported

Feb 20, 2012 10:43 AM

  Latest reply: Pat Willener, May 28, 2012 6:38 PM
Replies 1 2 Previous Next
  • Currently Being Moderated
    Mar 9, 2012 1:04 AM   in reply to J Fortune

    J Fortune wrote:

     

    andyross63 wrote:

     

    Instead of all this wrapper stuff, how easy (or hard) would it be to copy the installed Flash files from another install on XP or whatever and put them on the Win2K computer. Is that all that is really needed? We just need to find out where the files actually are and which ones need to be updated.

     

    and what registry entries need to be modified. I agree with this line of thought. I searched extensively for some information on a "manual installation" method.

     

    Maybe if someone from Adobe could post a comprehensive list of the install files, where they need to be located, and any additional requirement (like modification to registry entries) we could create a "manual installation" method that would allow updates to be made to W2K installs without needing to resort to wrappers just to run the installer. Anyone have this information?

    You don't need any manuall installation if Adobe offers a special version with an older installer for W2K. Meanwhile using a wrapper is the easiest, and for me the best, way to update Flash Player on Windows 2000. It's easy enough so that anyone can follow the steps to get a working result.

     

    I just updatet my Flash Player on my W2K-machine yesterday and it was just throwing the update file in the bin-folder of my still existing wrapper-directory from my first installation (http://www.ortwinpinke.de/2012/02/29/adobe-flash-player-11110262-unter -windows-2000-installieren) and starting the setup. Since only the setup and not Flash Player uses new dll-functions this will work perfect.

     

    Regards from germany

     

    Ortwin

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 9, 2012 7:11 AM   in reply to Pat Willener

    For what it's worth, the "regshot" utility (see http://sourceforge.net/projects/regshot/ ) may be helpful in identifying registry and system changes by taking appropriate "snapshots" both before and after Flash player is installed.

     

    J Fortune -- "Beucephous" here (how did you know?  ;-D ) -- with respect to the removal of kernel32.dll from the ExcludeFromKnownDlls list (assuming someone later wanted (for whatever reason) to "undo" the changes that "kdllinst.exe" makes), do you think the "UNINSTALL_WRAPPER.BAT" file (which uses the "ClearExcludeFromKnownDlls.reg" and "FixPath.vbs" files in the "install" subdirectory of the "win2k_xp_v1_10" program suggested above in this thread) would do the trick as well with the "kdw096k.zip" archive that you suggested?

     

    I'm thinking of trying your suggestion ("kdw096k.zip" archive) on my "test machine" to see if I can install the very latest version (11.whatever) of Flash without getting the "dynamic link library d3d9.dll could not be found in the specified path" error I got when I tried the "http://oldcigaret.info/win2k/files/win2k_xp_v1_10.zip" method.  If when I try it I still get that error, is it as easy a getting a "d3d9.dll" file from somewhere (e.g., a nearby WinXP pc) and copying it into the "temp folder of my choosing" with all the other DLLs?

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 9, 2012 4:07 PM   in reply to AcroNot

    Acro,

     

    I am not familiar with the "UNINSTALL_WRAPPER.BAT" from the OldCigarette Wrapper Pack v1.10 as I have used the KDW. You can get some info on the OCW here: http://oldcigaret.info/win2k/phpBB3/viewtopic.php?f=6&t=7 and there is info on the KDW here: http://oldcigaret.info/win2k/phpBB3/viewtopic.php?f=6&t=292 . But I do believe that the creators of both these wrapper packs have included the option to remove the changes that are made. If this is a high concern you should test the install/uninstall on your "test machine". In the end I think you could always use regedt32 to remove any dlls from the ExcludeFromKnownDlls list if need be. 

     

    I think the two wrapper packs are similar in their capabilities, but different in their implementation. The OCW I think was created initially for installing games on win2k systems and the KDW has more of an emphasis on application support, but in the case of the flash installer I think either will work as they both have support for the SetDllDirectoryW call.

     

    I started looking into the wrapper APIs originally because my install of Dropbox on win2k machines was missing the context menu. There was a dependency issue in DropboxExt.14.dll for a missing call in the win2k version of dbghelp.dll. Through some helpful posts on the dropbox site (http://forums.dropbox.com/topic.php?id=32134&replies=9) I was informed of the KDW which has a utility called rplbfile.exe. This will rewrite the dependency tree. With this I was able to take a dbghelp.dll file from a winxp install (which has the calls needed for implementing the context menu), rename it (dbgheXP.dll), place it in the dropbox bin folder, and use rplbfile to patch the DropboxExt.14.dll file so that it uses the dbgheXP.dll file in the bin folder instead of the win2k dbghelp.dll. So after having the KDW files and investigating it I thought it was easier to just use those to attempt to fix the issue with the abode installer.

     

    To answer your last question I have checked my machines and I do have d3d9.dll in the %WINDIR%\system32\ folder. You may want to check if you have the file located there as it may be missing from your "test machine" install or need to be re-registered. It also should work if you place the file in the same folder from which you are running the installer. I have done my own testing and in the end have used the KDW wrapper method on my real win2k install. I have the current (11.1.102.63) update installed and running.

     

     

    OldPerl  wrote:

     

    I just updatet my Flash Player on my W2K-machine yesterday and it was just throwing the update file in the bin-folder of my still existing wrapper-directory from my first installation (http://www.ortwinpinke.de/2012/02/29/adobe-flash-player-11110262-unter -windows-2000-installieren) and starting the setup. Since only the setup and not Flash Player uses new dll-functions this will work perfect.

     

     

    I agree with OldPerl that this is an option. If you set up a folder (either with his method or the EZInstall from KDW) in the future you can just drop the update files in there and run the installer. This would be one reason to not uninstall the wrapper. It is my belief (from feedback from BlackWingCat, the creator of KDW) that the wrapper dlls will only be used by APIs making function calls that are located in the folder to which the wrapper dlls have been installed. All others will use the win2k original dlls located in the %WINDIR%\system32\ folder. I am guessing this would be a higher concern for someone who actively runs installs on a win2k machine. My "installing" these days, at least on the win2k machine, is really only updates for flash, java, firefox, and a few other previously installed packages.

     

    I hope this helps.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 9, 2012 5:51 PM   in reply to J Fortune

    Yes, J Fortune -- that information is helpful.  I do appreciate it and will look into those links you provided later.

     

    I have an update.  I found a copy of the "d3d9.dll" file on "my" Windows 2000 pc (in case anyone is interested, it has the MD5 hash of:  "0e51bd586d186f61a9e4453db8aec774"), and I copied it into the same place (the system32 folder) on my test machine.  I was then able to successfully install the very latest version (11) of the Flash player on it for both Internet Explorer (using the original OCW method) and for non-IE browsers like Firefox and Opera (using the KDW method, just for fun).  I'm not sure why the d3d9.dll file was missing from my test machine.

     

    The interface from the KDW method has quite a bit going on there, so thank you again for the tips on using it to perform the EZ install.  I'm not sure which method I like better (both have their merits), but I do like the built-in ability of the OCW method that allows its removal if desired.  The KDW method is easy to remember, too -- just remember the kernel32 topmost setting, the EZ checkbox, the installation location and finally the Ez Install button.  I'm not sure what its "uninstall mode" button is for, but as I said above I'll check those links provided for more information.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 9, 2012 6:59 PM   in reply to AcroNot

    Acro, The way I understand it: If you re-run the EZ Install with all the same options as the first install, but check the "Uninstall mode" it will reverse the changes. I have not tested this. It might make sense for you to check it out on your "test machine" and post back. I will try to contact BlackWingCat and verify also.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 10, 2012 12:54 PM   in reply to Pat Willener

    Thank you Pat!  Following the instructions posted in post #21 I had a failure still but then rebooted, and then it worked fine to install version 11 on a Win2K SP4 system, though it then warned me of an incompatiblity with a Realplayer updater which is suspicious, but whatever. 

     

    Now I ask, is there any negative effect to just leaving this wrapper thing installed?  Seems like it would be handy to have around if the next Flash version installer has the same issue.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 10, 2012 3:27 PM   in reply to Ninja Cats

    Ninja Cats wrote:

     

    Thank you Pat!  Following the instructions posted in post #21 I had a failure still but then rebooted, and then it worked fine to install version 11 on a Win2K SP4 system, though it then warned me of an incompatiblity with a Realplayer updater which is suspicious, but whatever. 

     

    Now I ask, is there any negative effect to just leaving this wrapper thing installed?  Seems like it would be handy to have around if the next Flash version installer has the same issue.

    Yes Ninja a reboot is required for the modifications to the registry to be applied.

     

    I have been getting the incompatibility warning about Realplayer for a while with past updates that ran fine using the standard installer, probably some old verison of realplayer installed before, so the warning should not be that suspicious.

     

    I plan on leaving the KDW wrapper files (you seem to have used the OCW wapper) in place in the folder where I installed them to use again if (read when) the next updates installer has the same SetDllDirectoryW issue (or any other issues).

     

    Glad you got the updates working.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 13, 2012 6:26 AM   in reply to Oldperl

    Oldperl wrote:

     

    Mrs Clift wrote:

     

    Hi Ortwin, clicked on your link but sadly my German is not that good Have same problem as M_Miller and would like some help. Will go and vote re bug,

    Thanks

    Hi Mrs Clift,

     

    sorry for that and for the late reply. I have not checked my subscriptions due to illness.

    I will try to add an english translation to my blog entry within the next days. Thx for your feedback.

     

    regards from germany

     

    Ortwin

    So for all non-German speaking people i just added an english version of my blog-article using OldCigaret wrapper to install Flash-Player-Updates.

    Please use this link http://www.ortwinpinke.de/en/2012/03/13/install-adobe-flash-player-111 10262-and-later-under-windows-2000/

     

    Feel free to add a comment, also if you will find any mistakes in my english.

     

    Regards from germany

     

    Ortwin

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 13, 2012 4:44 PM   in reply to Oldperl

    Oldperl... just a mistake in the creation of the link above, as it has an extra http:// at the end of the embedded link that causes the page to not load correctly:

     

    Corrected link for previous post

    http://www.ortwinpinke.de/en/2012/03/13/install-adobe-flash-player-111 10262-and-later-under-windows-2000/

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 14, 2012 7:53 AM   in reply to M_Miller12345

    Hi,

     

    I have Windows 2000 pro.

     

    I got the same  error when installing the update.

     

    I uninstalled Flash Player and have now re-tried installing the  Flash Player.

     

    10.3.183.16

     

    from  http://get.adobe.com/flashplayer/

     

    Getting the error :

     

    " Procedure entry point SetDIIDirectoryW could not be located in dynamic link library kernel32.dll  "

     

    I'd appreciate it if Adobe  could kindly solve this problem.

     

    It was so easy before. Now I am not sure .  The procedures which have been kindly suggested are too complicated.

     

    I have uninstalled the old program by mistake thinking that the new software will have the missing file !  No flash player at all on my system now !

     

    Thanks

     

    JM_fab

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 14, 2012 8:13 AM   in reply to JM_fab

    I agree with JM_fab. It warmed my cockles to discover so many people wanting to help but I'm not going to try and poke around (see, I know the technical term) in directories and whatnot. Adobe should have an update available that works on Win2K etc. I have now given up so thanks again for all replies but I still don't understand what I'm supposed to do? Thank you also to Ortwin for adding an English version, I am sure it will be beneficial to others but sadly, not me! Ps, Ortwin, I hope you're feeling better!

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 14, 2012 11:59 AM   in reply to JM_fab

    Here are the latest Win2K compatible versions of 11.1.102.55:

    IE: http://www.filehippo.com/download_flashplayer_ie/10987/

    Others: http://www.filehippo.com/download_flashplayer_firefox/10991/

     

    Personally, I have always downloaded the stand-alone installers, and put them in an archive directory. Since they always use the same name, I have to use subdirectories with the version numbers. I do that with alot of software, and it's made it easier to backtrack when a newer version has problems.

     

    If Adobe has official copies of older versions available, please post the links in case users do not want to rely on a 3rd party site.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 14, 2012 1:49 PM   in reply to andyross63
     
    |
    Mark as:
  • Currently Being Moderated
    Mar 14, 2012 4:07 PM   in reply to J Fortune

    It should be mentioned the Adobe archive link leads to .ZIP files that contain all platforms for each version. The 11.1.102.55 archive is 175M.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 14, 2012 4:27 PM   in reply to andyross63

    andyross63 wrote:

    Personally, I have always downloaded the stand-alone installers, and put them in an archive directory. Since they always use the same name, I have to use subdirectories with the version numbers. I do that with alot of software, and it's made it easier to backtrack when a newer version has problems.

     

     

    I just copy the version # before downloading and paste it into the filename box on the download so they're already identifiable w/o subdirectories.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 15, 2012 10:50 AM   in reply to J Fortune

    J Fortune wrote:

     

    Oldperl... just a mistake in the creation of the link above, as it has an extra http:// at the end of the embedded link that causes the page to not load correctly

    Thx a lot. It's stupid that you cannot edit your own postings after some time!

     

     

    Mrs Clift wrote:

     

    Thank you also to Ortwin for adding an English version, I am sure it will be beneficial to others but sadly, not me! Ps, Ortwin, I hope you're feeling better!

    Your welcome Mrs Clift. I hope it will help other non-german-speeking people. And thx for the well wishes, I'm feeling better again.

     

    Regards from germany

     

    Ortwin

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 18, 2012 11:23 AM   in reply to J Fortune

    i just wanted to add to this thread... i did go over to the bugs entry and voted even though it has been closed, withdrawn and set as a featureremoval... i also followed J's post from over there about using the wrapper... it works well and i have just updated one of my w2k machines from whatever it was that broke before to 11.2.202.233 as can be seen in the attached photo...

     

    flash-wrapper.png

     

    i also wanted to add that from my reading, the wrapper package by old cigarrette was an inspiration to that used in the KDW package that J Fortune found and used... i like that there are wrapper dlls like these that handle the new calls and pass on to the old calls when necessary... excellent work to those involved and a big thanks... one can see my comments in the bug entry, too... there are some there that i've not made here

     
    |
    Mark as:
  • Currently Being Moderated
    May 18, 2012 11:46 AM   in reply to JM_fab

    My workaround is very simple: run any hex editor (e.g. Hiew), open InstallFlashPlayer.exe, find SetDllDirectoryW and change it to GetModuleHandleW

     

    Regards!

     
    |
    Mark as:
  • Currently Being Moderated
    May 21, 2012 4:52 PM   in reply to notbebe

    notbebe,

     

    Thank you for your workaround!  You are a SUPER GENIUS!  Even better than Wile E. Coyote!

     

    Mrs. Clift, are you still reading this thread?  Doing the workaround suggested by notbebe is as easy as editing a long text document using a word processor, searching for something in it like "I have a gray dog." and then changing that text to something similar like "I miss my old cat."  After changing the text, you save the changes and you're done.

     

    The only differences are that you're not using a word processor (you're using a very simple "hex editor" like "HxD") and it's not a text document you're editing (it's the latest Flash Player installer program).

     

    I'll try to provide instructions that should be easy to follow.  Here we go!

     

    Do a google search for HxD (that's capital H, small x, capital D) and download and install that program.  The link to the pertinent website I have from my installed copy of this free program (Version 1.7.7.0) is:  http://www.mh-nexus.de

    Tell it to put a shortcut on your desktop when it asks.  The shortcut's icon will look like a green capital letter H, a black small letter x, and a white capital letter D on an orange background.

     

    Then download the (latest) Adobe Flash updater program you'd like to install.

     

    For Flash Player 11 for Internet Explorer, use the following link:

    http://get.adobe.com/flashplayer/completion/?installer=Flash_Player_11 _for_Internet_Explorer_(32_bit)

     

    For Flash Player 11 for other browsers (like Firefox or Opera), use the following link:

    http://get.adobe.com/flashplayer/completion/?installer=Flash_Player_11 _for_Other_Browsers_(32_bit)

     

    Now you have the Flash program(s) that give you that crazy-looking error mentioned at the top of this thread when you try to run them on your Windows 2000 pc on which you haven't felt ready to go through the various steps (explained in earlier postings) needed to apply the "wrapper" patches.

     

    Never fear -- you can now EDIT those files so they WILL run on your Windows 2000 pc's as they are!

     

    Let's assume that you've downloaded the file to apply the latest version of the Adobe Flash Player to your Internet Explorer web browser.  That file would be named:   install_flash_player_ax_32bit.exe

     

    Open the HxD editor you've installed and do (only) the following after it opens:

     

    Click on File, Open (or press Ctrl+O on your keyboard, if you prefer) and browse to the folder containing the install_flash_player_ax_32bit.exe file.  Double-click that file in the Open dialog box to open it.  You'll see a funky screen with blue numbers along the left and across the top, 16 columns of "base 16" numbers (that's what hexadecimal means, hence a "hex" editor), and lots of "gibberish" in another 16-characters-wide section on the right.  Don't be intimidated by any of this.  It's like opening your car and looking at the engine and all the gizmos under the hood.  If all we want to do is check the oil and leave the other stuff alone, we'll be fine.  :-)   So that's what we're going to do.

     

    We are going to search for the "SetDllDirectoryW" text and change it to "GetModuleHandleW" and then we are going to save this change and quit.  That's all.  Just like the text example I cited above.  Simple.

    Just like checking the oil in a car, only not as messy.  :-)

     

    Press the F3 key.  This is the "Find again" shortcut in the HxD editor.  Since this is the FIRST TIME you're doing this, it won't "remember" anything to find from before.  This is where you (very carefully, because it will "remember" and you won't have to type the whole thing again anymore) type into the "Search for" box the text for which you want to search, i.e., typeSetDllDirectoryW

    You should read that as "set dee el el directory double you"  (DLL is geek speak for something called a Dynamic Link Library.)  I don't know if "case" matters -- I just typed it the way notbebe gave it above.

     

    It should look something like this (I'm showing the text highlighted):

    http://www.arbornet.org/~ncweb/4flash/1--F3_means_Find_again.jpg

    Then click on the "OK" button (or press the "Enter" key on your keyboard).

    You should then see something like this:

     

    http://www.arbornet.org/~ncweb/4flash/2--after_the_F3_find.jpg

     

    Crazy at it may seem, those hexadecimal numbers (53, 65, 74, 44, 6C, 6C...) actually correspond to the letters we understand a little better (SetDll...).  Here is where you will very carefully edit them.  Remember -- we're only changing SetDllDirectoryW to GetModuleHandleW (and nothing else).  Some of the letters in these 16-character groups are the same, and some are different.  The ones that you will change will be shown in red where they differ from the originals.

     

    VERY CAREFULLY click your mouse in the "section on the right" where you can see the "SetDllDirectoryW" letters.  Try to click just before the capital letter "S" when you do this.

     

    Then VERY CAREFULLY type ONLY:  GetModuleHandleW so that those 16 characters replace the 16 characters in SetDllDirectoryW.  You don't even have to type the final "W" since it's the same.

     

    When you've typed those "replacement letters," it should look like this:

    http://www.arbornet.org/~ncweb/4flash/3--after_changing_text.jpg

     

    See how the changed letters (and their hexadecimal "counterparts") are shown in red?  Check to make sure you didn't mistype anything.  YAY -- you're done typing!  (If you happen to make a mistake, you should be able to easily correct it.  If for whatever reason things ever look like they're totally out of hand, you can always quit (without saving changes) and start over.)  Now all you have to do is save your changes!  Let's save the changes the following way to keep it simple:

     

    Close out the HxD program by clicking on its "close button" -- the "X" in the far upper right corner -- the one "on top of" the other one.   When it asks if you want to save the changes, click Yes.

     

    HxD is such a nice hex editor that it AUTOMATICALLY saves a BACKUP of the ORIGINAL file in case anything went wrong!  (That backup has a file suffix that ends in ".bak" so you can easily tell.)

     

    Not only that, but now anytime you edit one of these Adobe Flash installation programs again and need to make the same change, all you'll have to do (since you did it properly the first time as I wrote above) after opening the file for editing is to press the following three keys to do the search:

     

    F3                    (Again, that is the F3 key, NOT the letter F followed by the numeral 3)

    Down-arrow       (Yes, the arrow on your keyboard that points down.)

    Enter

     

    All you have to remember is to type GetModuleHandleW as the replacement text (and save the changes).  Now you can download the Flash installer, tweak it, and run it without any problem on your pristine Windows 2000 pc, and you'll be up-to-date!  (Say it over and over to yourself to memorize it:  "Get module handle double you"  (or just copy it to a text file so you remember what it is).

     

    This should work well for you.  Have a nice day.  Please say a prayer for me and my family.  (My uncle died last month and the named executor of the will is currently being kind of nasty to the rest of us.)

     

    Sincerely,

    AcroNot

     
    |
    Mark as:
  • Currently Being Moderated
    May 21, 2012 4:56 PM   in reply to AcroNot

    If it's too hard to scroll to see those wide illustrations shown in my posting above, you may find them here:

     

     

    http://www.arbornet.org/~ncweb/4flash/2--after_the_F3_find.jpg

     

    http://www.arbornet.org/~ncweb/4flash/3--after_changing_text.jpg

     
    |
    Mark as:
  • Currently Being Moderated
    May 22, 2012 4:01 AM   in reply to notbebe

    nice catch... odd that something so simple would cause so many problems.

    I already have the "wrapper" set up and am using it, but I will keep this in the toolbox..

     

    @Acro.. thanks for the detailed write up for those who need it. On a side note, sorry to hear about your uncle. I hope everything works out OK.

     
    |
    Mark as:
  • Currently Being Moderated
    May 23, 2012 12:02 PM   in reply to notbebe

    RE: notbebe,  on May 18, 2012 12:46 PM

    EXCELLENT.  Simple. Easy. It Worked. Fast (only one replacement/substitution required). Efficient.

    KUDOS to you and all who follow in your bloodline.

    Cheers and thanks,

    M

     
    |
    Mark as:
  • Currently Being Moderated
    May 27, 2012 5:18 PM   in reply to Chris Campbell

    I am having the same problem on my client's very old W2K SP4 machine. Please fix it, Adobe!

     
    |
    Mark as:
  • Currently Being Moderated
    May 27, 2012 5:54 PM   in reply to AntD00d

    AntD00d wrote:

     

    Please fix it, Adobe!

    This topic has enough instructions for you to fix it yourself.

     
    |
    Mark as:
  • Currently Being Moderated
    May 27, 2012 6:29 PM   in reply to Pat Willener

    Pat Willener wrote:

     

    AntD00d wrote:

     

    Please fix it, Adobe!

    This topic has enough instructions for you to fix it yourself.

    Are those workarounds even supported by Adobe? They look like hacks to me.

     
    |
    Mark as:
  • Currently Being Moderated
    May 27, 2012 11:18 PM   in reply to AntD00d

    As I wrote in the other topic, Windows 2000 is no longer supported.

     

    It is a hack, making the installer look for an entry point that exists in W2K.

     
    |
    Mark as:
  • Currently Being Moderated
    May 28, 2012 6:16 AM   in reply to Pat Willener

    Pat Willener wrote:

     

    As I wrote in the other topic, Windows 2000 is no longer supported.

     

    It is a hack, making the installer look for an entry point that exists in W2K.

    Interesting. So even the latest v10.3 is unsupported for W2K SP4? Wow.

     

    What's the latest version that will install and work in Windows 2000 SP4 that doesn't require hacking then? V10.3, downloaded from Adobe's web site, doesn't install in it.

     
    |
    Mark as:
  • Currently Being Moderated
    May 28, 2012 7:32 AM   in reply to Chris Campbell

    Chris, that web page says Flash Player 10.1.102.64 is the latest but how come Adobe's web site's http://get.adobe.com/flashplayer/?promoid=BUIGP gives me this in Firefox v12?

     

    "Adobe Flash Player 11.2.202.235 (3.94 MB)

     

    Your system: Windows 32-bit , English, Firefox"

     

    Obviously, this installer gives me the same error.

     

    Chris Campbell wrote:

     

    I did have it updated on our Archived Flash Player Versions page,  is there another location I should change?

     

    Thanks,
    Chris

     
    |
    Mark as:
  • Currently Being Moderated
    May 28, 2012 8:16 AM   in reply to AntD00d

    Technically, Win2K is NOT supported for Flash 11.x, and never was. We were just lucky that it did work.

     

    The real issue is not with Flash itself, but the installer.

     
    |
    Mark as:
  • Currently Being Moderated
    May 28, 2012 8:52 AM   in reply to andyross63

    andyross63 wrote:

     

    Technically, Win2K is NOT supported for Flash 11.x, and never was. We were just lucky that it did work.

     

    The real issue is not with Flash itself, but the installer.

    Interesting. I always got v10.3 from its web site in the past, so I assume v11.x would not work at all. Today, v11 is offered. Now, v10.3 won't install. Sheesh!

     
    |
    Mark as:
  • Currently Being Moderated
    May 28, 2012 9:07 AM   in reply to AntD00d

    That's the really stupid problem. When they updated 10.x (which is still supported by Adobe) for the latest security issues, they also updated the installer.

     
    |
    Mark as:
  • Currently Being Moderated
    May 28, 2012 9:35 AM   in reply to andyross63

    andyross63 wrote:

     

    That's the really stupid problem. When they updated 10.x (which is still supported by Adobe) for the latest security issues, they also updated the installer.

    Hence, why this is a bug. Adobe messed up! Why should we go back to v10.1? Sheesh.

     
    |
    Mark as:
  • Currently Being Moderated
    May 28, 2012 6:38 PM   in reply to AntD00d

    This is not a bug!  Should Adobe also still support Windows 95?  Or Windows 3.1?

     

    Technology moves forward, and at some point it simply becomes hopeless to provide backwards compatibility for outdated systems. Windows 2000 was released 13 years ago; Microsoft has ended support for it two years ago, so why should other software makers continue to support it?

     

    This topic is now closed.

     
    |
    Mark as:
1 2 Previous Next
Actions

More Like This

  • Retrieving data ...

Bookmarked By (1)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points