Content Type
Profiles
Forums
Events
Everything posted by jaclaz
-
Good . let's wait for the OP to detail what he actually has in his hands. As side-side note, Panduit stuff is generally speaking very good, but navigating their catalogs is IMHO usually a nightmare, they have a crazy way of naming things and they continuosly (or way too often for my tastes) change models (and names) . jaclaz
-
Yep, as I see it: Vista is a bettered XP, only worse 7 is a bettered Vista, actually better 8 is a bettered 7, only much, much worse 8.1 is a bettered 8, only worse 10[1] is a bettered (and bettered, and worsened and updated, and re-realeased and re-bettered and re-worsened) 8.1, actually better[2][3] jaclaz [1] thanks to continuous updates/changes you never know what you are actually running [2] actually bettering 8.1 is kid's play [3] though there is still a loooong way to get to the levels 7 reached.
-
Yes, you see the value: OSversion REG_SZ 3.6.1.0.0 in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\AdvancedOptions\CRYPTO\TLS1.2? Select it (left click), then Right click and choose Delete. Do the same with the same value in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\AdvancedOptions\CRYPTO\TLS1.1 Then check again Internet Properties. You can have the same effect if you merge the .reg file on https://johnhaller.com/useful-stuff/enable-tls-1.1-and-1.2-on-windows-vista or the copy I posted here (again, it is not difficult, select the following: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\AdvancedOptions\CRYPTO\TLS1.1] "OSVersion"=- [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\AdvancedOptions\CRYPTO\TLS1.2] "OSVersion"=- open a new Notepad, Paste then save as modtls.reg, then merge into the Registry) If for whatever reasons the .reg file is not registered on your machine for merging to the Registry, in Regedit File->Import->select the modtls.reg->OK) Manually or through the .reg file, these two values: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\AdvancedOptions\CRYPTO\TLS1.1\OSVersion HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\AdvancedOptions\CRYPTO\TLS1.2\OSVersion need to be deleted from your Registry in order to have TLS1.1 and TLS1.2 available in Internet Properties. Now, let's see if I can explain to you the issue you are having. Under Windows 7 TLS 1.2 is enabled in Internet Properties. Nonetheless, still in Windows 7, Firefox does NOT use THAT TLS 1.2 but rather its own. Under Vista right now you can connect with Firefox (that still use its own TLS 1.2) but then, when the Flight1.com server wants to communincate, it uses *some other* TLS 1.2 (most probably the files related to IE9/Internet Properties), and since these latter are not enabled, it gives the error. jaclaz P.S.; if you have difficulties in downloading the file from http://johnhaller.com/sites/default/files/downloads/reg/vista-tls-1.1-1.2-update.reg I am attaching it inside a .zip file. extract it and merge it. vista-tls-1.1-1.2-update.reg.zip
-
Yep, unless in the meantime something new has come out (or until something new come out) those were the cards we could play. jaclaz
-
Yep, which means - as expected - that the issue is not TLS 1.2 in itself (as a protocol for browsing) but rather that the *whatever* system IS3 uses makes use of *something* (possibly actually the IE9 "engine" or "subsytem") and that this latter might need to be TLS 1.2 enabled (and possibly something else), So, back to work. Did you finally manage to install the KB4056564 successfully? AFAIK if your system is 64-bit, then you must have the WOW6432Node, unless the OS has been heavily modified, (and even if you hadn't it before, the update should have added it). Since - reportedly - the update creates the keys in HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\AdvancedOptions\CRYPTO\ that registry path must exist. On the other hand, if your OS is actuallt 32 bit the 64-bit wouldn't install. The 32-bit version would create the: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\AdvancedOptions\CRYPTO\TLS1.1 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\AdvancedOptions\CRYPTO\TLS1.2 paths, that you also don't have, so maybe - and for *whatever reasons* the issue is that on your system the KB405654 didn't install properly. Maybe there is a pre-requisite of some other updates? jaclaz
-
backside picture of what? It doesn't look like a puchdown one, here there are pictures of the specific model: https://www.cableorganizer.com/panduit/patch-panels.htm It seems like connections are 4+4, similar to the ones in this video: jaclaz
-
Maybe we need to re-start from the beginning? Forget for one moment IE9 and TLS 1.2 support in Internet Properties. Fire up Firefox on that machine. Open with it this URL: https://clienttest.ssllabs.com:8443/ssltest/viewMyClient.html scroll down until you see "Protocol Features/Protocols". Do you find: TLS 1.2 Yes (in green)? If yes, your current Firefox is using TLS 1.2 allright, then you can try connecting with it to your Flight1 account to validate your purchase. Post errors (if any) you get when you try to connect to that Flight1 account. jaclaz P.S.: as a side note, do check your Vista install "bitness": https://hk.canon/en/support/8100077700 Normally a 64-bit install needs to have the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node in oreder to support 32 bit applications, there are very rare cases of "lited" install with the 32 bit subsystem remoevd, but I doubt it is your case.
-
This one? http://www.panduit.com/heiler/SpecificationSheets/D-COSP228--WW-ENG-dp5epatchpanel-WEB.pdf AFAICT it comes "not-wired", and it would make no sense to have the Punchdown tool: PDT110 as accessory: https://www.panduit.com/en/products/copper-systems/connectors/connector-tools-accessories/pdt110.html if this wasn't the case. The patch panel is intended to provide an easy to connect/disconnect (RJ-45 sockets) but "on the back" these are not connected to anything (until you assemble it - say - in a rack and connect the cables). jaclaz
-
No , I did NOT make that decision, you made it and I totally and utterly disagree with it. That equates to giving up (which is not an option). Anyway, whatever floats your boat is fine . jaclaz
-
Yep , don't worry, no harm was done. jaclaz
-
Fine. Let me rephrase. From new info supplied by lmacri: @terryindorset I now believe that: 1) the actual needed files/protocols/whatever for having TLS 1.2 in Internet Explorer AND in the connected rendering engine/whatever are in the KB4056564 you installed. 2) Firefox simply uses them its own TLS 1.2 files "directly" 3) Internet Explorer is prevented from using them (and thus you cannot see them in "internet Properties") because of the two keys that you need to delete So, from what I can understand, you have now working TLS 1.2 in Firefox and NOT working in IE. Then, it is entirely possible that: a. your *whatever* flight simulator thingy site works now just fine in Firefox or b. it needs anyway to connect to IE9 and it settings or c. it won't work even once IE9 properties show TLS 1.1 and TLS 1.2 unless some other changes/tweaks/updates/whatever are implemented. If you prefer your question is actually 3 questions: 1) can I use Firefox on a site with TLS 1.2 <- Yes, now that you have downloaded and installed the update (The sslabs view shows TLS 1.2. ) 2) can I have TLS 1.1 and TLS 1.2 in the IE9 Properties?<-Possibly yes, now that you have downloaded and installed the update, but only once you will have removed the two keys 3) can I have IS3 working on Vista+Firefox? <- No idea, it is well possible that you will need anyway to use IE9, or the TLS1.2 is only one of the requirements. And you are at this moment at #1. The central point doesn't however change much, i.e. It is still possible any of: 1) installing the update was not necessary and everything works in Firefox "as is" 2) that Internet Explorer 9 (AND the update AND the two Registry keys deleted) are actually needed 3) the two above might not be enough and something else is needed to actually do the IS3 *whatever* you need to do jaclaz
-
I see now . The empty string reference is misleading. Registrar Lite (old 2.00) produces a "better" error "Values of type REG_MULTI_SZ are not allowed to contain empty lines. Remove them?" Technically "empty string" is appropriate, as the value in binary is an actual string, 00 terminated, and a double 00 00 means "end of value", but in default view the Registry editor renders the 00 as "newline", so "empty line" is more descriptive of what you see. Newer Registrar Lite (6.50) removes the "newline" without warning Try this one : http://aezay.dk/aezay/regcmd/ jaclaz
-
You are welcome, BUT: come on, take it easy man , Vistapocalypse is only trying to help you, since the matter is far from being simple/linear it is perfectly normal that willing helping members post doubts, request for confirmations, theories, ideas (crazy or not so crazy), it is the normal process of brainstorming to solve a problem, particularly when the problem is "officially" not resolvable (by MS or by the guys that provide the IS3 of by your local computer support people). jaclaz P.S.: It is rarely the case (but you never know) check that you are using the "right" version of Regedit (i.e. if you are using one, try the other one), among the most confusing explanations on earth (brought to you by the good guys that put in WOW64 32 bit programs and that call "system" the volume that boots and "boot" the volume that contains the operating system): https://support.microsoft.com/en-us/help/305097/how-to-view-the-system-registry-by-using-64-bit-versions-of-windows
-
@terryindorset I believe that: 1) the actual needed files/protocols/whatever are in the KB4056564 you installed. 2) Firefox simply uses them "directly" 3) Internet Explorer is prevented from using them (and thus you cannot see them in "internet Properties") because of the two keys that you need to delete So, from what I can understand, you have now working TLS 1.2 in Firefox and NOT working in IE. The paths are: 32 bit: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\AdvancedOptions\CRYPTO\ 64 bit: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\AdvancedOptions\CRYPTO\ Check this latter path. Then, it is entirely possible that: a. your *whatever* flight simulator thingy site works now just fine in Firefox or b. it needs anyway to connect to IE9 and it settings or c. it won't work even once IE9 properties show TLS 1.1 and TLS 1.2 unless some other changes/tweaks/updates/whatever are implemented. If you prefer your question is actually 3 questions: 1) can I use Firefox on a site with TLS 1.2 <- Yes, now that you have downloaded and installed the update (The sslabs view shows TLS 1.2. ) 2) can I have TLS 1.1 and TLS 1.2 in the IE9 Properties?<-Possibly yes, but only once you will have removed the two keys 3) can I have IS3 working on Vista+Firefox? <- No idea, it is well possible that you will need anyway to use IE9, or the TLS1.2 is only one of the requirements. And you are at this moment at #1. @Vistapocalypse Allow me to doubt that a restore point exists (or - even if it exist - it can be found): jaclaz See edited post below.
-
As often happens a surely accidental little mistake is (has been, and will be) perpetuated forever until someone actually corrects it EXPLICITLY. This: is WRONG. The correct path is: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\AdvancedOptions\CRYPTO\TLS1.1 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\AdvancedOptions\CRYPTO\TLS1.2 See this updated thread: https://msfn.org/board/topic/181705-solving-vistas-lack-of-tls-11-or-12/ And this reference one: https://www.vistax64.com/threads/ie9-last-supported-browser-for-vista.305228/ jaclaz
-
I don't know, I just reported what I found, generally speaking WinClient5270 posts are accurate, but of course there can always be an exception to the rule, possibly a typo but yes, confirmed (sort of), the correct path is: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\AdvancedOptions\CRYPTO\ https://www.vistax64.com/threads/ie9-last-supported-browser-for-vista.305228/ jaclaz P.S.: I corrected the .reg file I posted earlier AND updated the original thread: https://msfn.org/board/topic/177994-tls-1112-and-vista-issue-no-options/
-
Well, Regedit is a rather simple tool. You open it, you can "run" regedit.exe from the start menu. https://www.digitalcitizen.life/run-window-windows-7-why-use-it-anymore You will see a two pane window. On the left you will see "hives" (imagine for the moment that they are folders in Explorer) You double click (in the left pane) on HKEY_LOCAL_MACHINE and the "folder" will open showing "sub-folders" (actually "keys") . You navigate down the tree, since you want to get to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\AdvancedOptions\CRYPTO\TLS1.1, you need to click on: Software Microsoft Internet Explorer AdvancedOptions CRYPTO TLS1.1 when you are there, on the right you will find a number of "files" (actually "values"), imagine that they are all .txt files, and that - like it would happen for a .txt file in Eplorer - if you double click on one it will open in Notepad to be edited. But you don't want to edit it, you should find in the right pane, under the "path": HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\AdvancedOptions\CRYPTO\TLS1.1 a "file" ("value") named "OSVersion". You can right click on it and in the pop-up menu choose "Delete". That's it, it is not in any way different from deleting a file in Explorer. Watch this (it is an XP but Vista - besides the looks - is not in any way different): jaclaz
-
Looking around, I have seen quite a few Task Scheduler replacements/alternatives, and (only to confirm that you are not the only one) quite a few people stating that the built-in Task Scheduler is "unreliable". A few: https://www.splinterware.com/download/index.html https://www.z-cron.com/download.html https://web.archive.org/web/2019*/http://www.theabsolute.net/sware/files/tasksched.exe a Java based one: https://www.oliver-matuschin.de/en/projects/task-till-dawn jaclaz
-
Normally you right click on the link and choose "Save as", anyway you can copy and paste the following and save it with Notepad as "vista-tls-1.1-1.2-update.reg" Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\AdvancedOptions\CRYPTO\TLS1.1] "OSVersion"=- [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\AdvancedOptions\CRYPTO\TLS1.2] "OSVersion"=- it is a simple .reg file that - once merged to the Registry - deletes the two OsVersion values. But the issue here may be (see my previous post) that the above is OK for 32 bit systems but for x64 you need other modifications, i,e. this .reg: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\AdvancedOptions\CRYPTO\TLS1.1] "OSVersion"=- [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\AdvancedOptions\CRYPTO\TLS1.2] "OSVersion"=- But since they are just a few changes, only involving deleting a value you can do the above manually with Regedit. jaclaz
-
Naah, don't worry, it is just a sketch, maybe 1/4 of the needed work, it needs to be made into actually producing the restore points, I have no idea where they are saved in Windows 7, and/or it is possible to use ISO yyyymmdd_hhmm (or there is instead the need to write to a log/database of sorts), needs to be tested, and possibly made "foolproof", checking for elevation/Admin credentials, and what not. The WMIC command to create a restore point should be something like: wmic.exe /Namespace:\\root\default Path SystemRestore Call CreateRestorePoint "MyRestorePoint", 100, 7 that would become in the batch wmic.exe /Namespace:\\root\default Path SystemRestore Call CreateRestorePoint "%now%", 100, 7 but that goes into the "description", not in the file name, so you will need to list descriptions, probably *like* here: https://www.tenforums.com/tutorials/131901-see-list-all-available-system-restore-points-windows.html jaclaz
-
... or you stop the background service or disconnect from the internet (but of course is much better to verify that the OS is patched to last updates ) jaclaz
-
Yep , exactly. Let's call it PHATS , (Poorman's Half-@§§ed Task Scheduler). A batch sketch: @ECHO OFF SETLOCAL ENABLEEXTENSIONS :: Use WMIC to retrieve date and time FOR /F %%A IN ('WMIC Path Win32_LocalTime Get /Format:list ^|FIND "="') DO SET my_%%A :: Check that today is one of the "blessed" days :: Every three days, this will however make a file on the 31st and one on the 1st of following month :: AND there is no check about how old is last file :: FOR /L %%A IN (1,3,31) DO IF %%A EQU %my_day% GOTO :do_something :: OR Monday, Wednesday, Friday FOR /L %%A IN (1,2,5) DO IF %%A EQU %my_DayOfWeek% GOTO :do_something ECHO Not the right day, today is %my_day%, day of week #%my_DayOfWeek% GOTO :EOF :do_something SET my_month=0%my_month% SET my_month=%my_month:~-2,2% SET my_day=0%my_day% SET my_day=%my_day:~-2,2% SET my_hour=0%my_hour% SET my_hour=%my_hour:~-2,2% SET my_minute=0%my_minute% SET my_minute=%my_minute:~-2,2% SET now=%my_year%%my_month%%my_day%_%my_hour%%my_minute% SET now FOR /F %%A IN ('DIR /b /O-N *_*.txt 2^>NUL') DO SET my_last=%%~nA&&GOTO :Out_of_loop :Out_of_loop IF NOT DEFINED my_last GOTO :do_cmd IF %now:~0,8% EQU %my_last:~0,8% GOTO :Error_1 IF %now:~0,8% LSS %my_last:~0,8% GOTO :Error_2 IF %now:~0,6% LSS %my_last:~0,6% GOTO :do_cmd SET /A Delta=%now:~0,8% - %my_last:~0,8% IF %Delta% GEQ 3 GOTO :do_cmd GOTO :EOF :do_cmd ECHO Imagine here a command that makes a restore point ECHO and *somehow* names it %now%.txt ECHO Something>%now%.txt GOTO:EOF :Error_1 ECHO Nothing to do, a today file exists. PAUSE GOTO:EOF :Error_2 ECHO Nothing to do, a later than today file exists. PAUSE GOTO:EOF jaclaz
-
I know that one per day i just "too much" and this is why i suggested to automate the making of a manual one through a conditional script that you can change so that the actual manual restore point is made ONLY when more conditions are met (two in the example, date and NOT an existing one): jaclaz