AstroSkipper
Content Type
Profiles
Forums
Events
Everything posted by AstroSkipper
-
I tried your fix. If I have understood you correctly, in the SelfHelper.jsm file, I should replace line 55 this.version = parseInt(AppConstants.MOZ_APP_VERSION); with the following one: this.version = 74; If so, then this does not fix anything. The only thing that happens is a lot of new ReferenceError messages "Service is not defined" in the Browser Console. Furthermore, I think that it is not the Custom Buttons extension that needs to be fixed, which runs properly under Firefox 74, but Mypal 68.14.8b. What do you mean by "hubbub"? Did you even read what I wrote? I consider such an answer to all my information, investigations and questions that I have put a lot of effort into to be absolutely inadequate. I have asked you a few questions, but have not received any answers. And once again, I no longer think the issue is related to a version mismatch. All is explained in the posts above and in my thread "Mypal 68 in Windows XP". Keyword: XBL But I will not repeat myself here.
-
@feodor2 I'm afraid that you've overshot the mark with your changes as you did in version 68.14.5b. With a probability bordering on certainty, there will be other "patients" who suffer from similar "symptoms" as is currently the case with Custom Buttons. Whatever the actual cause, I hope I could help you with my investigations and information.
-
@feodor2 Although Mozilla does and has done things to their Firefox browser for years that I personally think are terrible, certain features, even if they are considered deprecated and not secure, will be retained for compatibility reasons. That's something positive. On the subject of XBL and binding, what about the CSS property -moz-binding in your new release? This property is also used by Custom Buttons. For example, for the code editor in the file codeeditor-cbeditor.css: cbeditor { -moz-binding: url(chrome://custombuttons/content/cbeditor.xml#custombuttons-codeeditor); } #accelkey { -moz-binding: url(chrome://custombuttons/content/cbeditor.xml#accelkeytextboxbinding); } Can Mypal 68.14.8b even cope with this?
-
Thanks for your reply! I investigated the code of Custom Buttons more deeply, and you are right, the Custom Buttons extension solely relies on the platformVersion, Since you removed the XUL stuff, you logically can't keep the platformVersion at 68. But your new release Mypal 68.14.8b has become somehow versionless. It doesn't behave as a Firefox 68 and it doesn't behave as a Firefox 74. It's a bit lost. Your browser tells Custom Buttons that it is Firefox 74, but it is not. Today, for this purpose, I have made a proof and installed Firefox 74 Portable on a Windows 7 Professional 64-Bit notebook, injected the two files config-prefs.js and config.js, and installed the legacy Custom Buttons extension. As I have already predicted, Custom Buttons runs perfectly under Firefox 74. The code editor is fully functional. The legacy Custom Buttons extension has always been compatible with much newer Firefox versions and is constantly being developed further. Here are two screenshots to demonstrate what the issue is about: Custom Buttons' broken code editor in Mypal 68.14.8b: Custom Buttons' fully functional code editor in Firefox 74.0.1: As I already said, you must have removed something that Mozilla did not. And I suspect it has something to do with XBL. Certain functions for binding XML files are required by the Custom Buttons extension for the code editor, which you have probably removed. That's why I said your new release is somehow versionless. Neither fish nor fowl. Sorry for that! The conversion from XUL to XHTML is no problem as you can see. Anyway! I hope you won't behave worse than Mozilla did in the past, and I urgently hope you will be able to restore a general version compatibility. And it doesn't matter which Firefox version you raise the platformVersion to as nevertheless the Custom Buttons extension should work then.
-
In comparison to Mypal 68.14.8b, I have executed the two JavaScript commands again in Mypal 68.14.7b: JavaScript commands: parseInt(Services.appinfo.platformVersion); Output: 68 parseInt(Services.appinfo.version); Output: 68 In any case, there is a clear version specification in the previous release.
-
Sorry but unfortunately, I have to disagree when it comes to Windows XP -> Windows NT 5.1 and Mypal 68. As you know, this topic here is about Mypal 68 in Windows XP . I have tested all possible Firefox version numbers by a SSUAO in Mypal 68.14.8b, and 128 was definitely the minimum to get rid of the yellow message box. Any version lower than 128 failed. Greetings, AstroSkipper
-
Here are some facts about versions inside Mypal 68.14.8b: JavaScript commands: parseInt(Services.appinfo.platformVersion); Output: 74 parseInt(Services.appinfo.version); Output: 68 ------------------------------------------ Some preferences in about:config: browser.migration.version: 94 extensions.lastAppVersion: 68.14.8 ------------------------------------------ General user agent: Mozilla/5.0 (Windows NT 5.1; rv:88.0) Gecko/20100101 Firefox/88.0 Mypal/68.14.8 68, 74, 88, 94 Neither fish nor meat (German saying). Or, neither fish nor fowl. The problem with this is that there have been some significant changes in the Firefox versions from 69 to 72. If an extension receives the wrong Firefox version at a certain point, this can of course lead to malfunctions. And that's exactly what I think might be the case with the Custom Buttons extension. The other theory, that something elementary has been removed, of course remains. Strangely enough, a few typical error messages relating to the cbeditor.xml file have completely disappeared. Maybe, this file can't be correctly processed now. Possibly due to @feodor2's remove of XBL?
-
Ok. This issue seems to belong to all old browsers. To get rid off this yellow message box, you need an updated user agent. Firefox 128 is now the minimum under Windows XP: Mozilla/5.0 (Windows NT 5.1; rv:128.0) Gecko/20100101 Firefox/128.0
-
@feodor2 Due to the changes in Mypal 68.14.8b, the Firefox Add-ons page shows the yellow message box even with compatible extensions "You need an updated version of Firefox for this extension". Here, for example, is the extension TWP - Translate Web Pages whose latest version 10.1.1.1 has a minimum version of 64: https://addons.mozilla.org/en-US/firefox/addon/traduzir-paginas-web/ TBH, this message is now displayed on all extension pages, and it doesn't matter whether the extension is compatible or not. So, what's going on here? Somehow, your browser seems to have become versionless.
-
@feodor2 Thanks for your new release Mypal 68.14.8b! I am currently testing this version more closely. Due to the complete removal of XUL and XBL, a lot has changed. I have already reported about it here. Similar to version Mypal 68.14.5b, the legacy Custom Buttons extension is no longer fully functional. The internal code editor is totally broken and therefore has become unusable. You can no longer access, view or edit the code with the extension. New custom buttons can't be created, either. The legacy Custom Buttons extension should actually also work in higher Firefox versions. It has corresponding XHTML files and compatible code that is made available via appVersion queries. It could be that an incorrect version is being determined, as version 68 or version 74 is displayed in Mypal 68.14.8b depending on the corresponding command. I checked that in the Browser Console. BTW, I really miss the Scratchpad which is also gone in your new release. Another guess I have is that you have removed something important that requires the legacy Custom Buttons extension. As you know, in Mypal 68.14.7b, the legacy Custom Buttons extension still worked. Maybe, you can take a look at it. BTW, what is the current level of JavaScript and CSS in Mypal 68.14.8b?
-
FYI, the Nuchi-Sporif UC.JS script loader, the best script loading method so far, presented in the first post of this thread for years, has stopped working with @feodor2's new release Mypal 68.14.8b. All other methods based on the Nuchi script loader won't work anymore, either. The Xiaoxiaoflood script loading method which is now recommended by @feodor2 is unfortunately the worst of all methods tested by me some months ago. I won't use it in any case and have changed to the Alice0775 script loading method in 4th place in my ranking list. Several scripts don't work anymore and have to be fixed due to all changes. Same applies to CSS stylesheets. I have already adapted a whole series of both to the "new" Alice0775 script loading method and to the new browser. @feodor2 seems to have removed XUL and XBL from Mypal 68.14.8b. Although the legacy Custom Buttons extension still can be installed, it is now somewhat broken. The internal code editor completely stopped working. And as expected, Xiaoxiaoflood's extension loader can't help either. That would have been a miracle if it had been different. I wish everyone lots of fun fixing scripts and stylesheets.
-
Thanks for replying! This is just a leftover and has now been edited by me. But the other announcements are correct and point to the most recent version.
-
A night's sleep always brings new ideas to light. The 7-Zip commands for extracting can be simplified to remain completely relative in the path information such as I already did in the whole ytBATCH for Windows XP script ensemble. I will implement this in the next release. Sometimes, things are that simple.
-
@Cixert Both your system error 3 and the message "permission denied" do not happen here in any case and therefore can't be reproduced by me. They seem to be related to your system only. So, solving that is up to you. On the other hand, the inability of correct unzipping on your drive D: was caused by a 7zip command which was actually relatively created by me but was unintentionally bound to drive C: exclusively. However, this had no negative effect on standard computers with C: as the system drive. That's why I didn't notice it. Anyway! ytBATCH for Windows XP should now be able to be set up automatically and without any errors (at least, no erros caused by ytBATCH for Windows XP), even on a non-standard computer as yours. Thus, thanks again for your report here and for being non-standard!
-
FYI, all releases of ytBATCH for Windows XP have been fixed by me so that the setup routine does not only work correctly on drive C: but also on any other drive. Please, re-download the desired release! ytBATCH for Windows XP 1.6 is currently the most recent, final release and recommended by me. Cheers, AstroSkipper
-
The current final is version 1.6. It was clearly announced. Where did you read anything about a beta? The versions 1.5 and 1.6 are final ones. The programme ytBATCH for Windows XP usually does not use any absolute paths but relative ones or those stored in system variables. When installing it, you can choose between the location stored in the system variable %ProgramFiles% or the current location of the extracted archive folder. When setting up on drive C:, it works fine. Of course, I didn't expect anyone to come up with the idea of setting it up on a different drive. The information that you tried to set up ytBATCH for Windows XP on other drive than C: is of course important. Thanks for that! You have exceptional skills and really came through here. And now, you get your special treatment. I had a short look into my code and directly found the cause of the inability to unpack both archives on a drive other than C:. I have tested it on my drive D: and then directly fixed the code. But no system error 3 or message "permission denied" here. @Cixert In which format has your D: drive been partitioned? Possibly in NTFS with some restrictions? I urgently need an answer to this question from you. P.S: I'm glad that there are individualists like you who do things differently from the rest of us. Thank you for that!
-
Your question can only be answered if you specify "a program". ytBATCH for Windows XP, for example, has an option to switch between youtube-dl and yt-dlp in the Preferences window. Just type Y. And it can also deal with playlists whose option can be toggled from false to true in the Enter Action window by the key P.
-
VT Hash Check - XP compatibility restored
AstroSkipper replied to genieautravail's topic in Windows XP
I think you misunderstood my comment a little. The sequence is not correct. First open the VTHash.exe with a double click, the window is then opened hidden and only then open a new Explorer window. For me and @genieautravail, the VTHash.exe window then becomes visible again on older computers. -
VT Hash Check - XP compatibility restored
AstroSkipper replied to genieautravail's topic in Windows XP
Intel Pentium 4 Northwood 2.80 GHz CPU (single core, 32 Bit), 1.5 GB SD-RAM and a NVIDIA GeForce 6200 graphic card. As I already mentioned, the hidden window appears again if I open an Explorer window. Very strange. -
I have completely changed and rewritten the original ytBATCH from eppic so that it now works perfectly with both YouTube downloaders youtube-dl and yt-dlp. All bugs and inconsistencies have been fixed by me. Especially the fact that the command line options of both downloaders are not identical, I have taken into account by assigning separate configuration files to each downloader. This allows the user to enter the desired options for each downloader and then receive the media files exactly as desired. ytBATCH for Windows XP is totally customised for the use of youtube-dl and yt-dlp, and ideal as a user interface for these two YouTube downloaders. And due to the new update module, the user can easily get the most recent versions of these two YouTube downloaders compatible with older OSes like Windows XP when ever wanted. This is very important regarding the permanent changes which are done by YouTube.
-
The latest official version of youtube-dl is from 2021. To get a more recent one, the user would have to compile an executable with all recent changes. Fortunately, @nicolaasjan has been doing this even for SSE only CPUs. When it comes to YouTube-DL Gui 0.4, I now have tested it again. Basically, it still works with both youtube-dl and yt-dlp. But the internal switches are from 2017 and cause problems. The subtitles option has to be switched off as it stopped working. The different, pre-adjusted switches for the video quality do not really work well. If you set 480p, you get something with 398p. To get the programme running smoothly again, the source code would have to be considerably revised and recompiled. ytBATCH for Windows XP, on the other hand, can be set so perfectly that you get exactly what you want.
-
@genieautravail Long time ago, I downloaded a package of DOS auxiliary tools. Inside this package was the Window.exe tool. I can't remember from where exactly. But I always download programmes only from trusted sources and developers. I now have large archives with all kinds of tools. These little tools are simply great and can be of help when programming new projects. A good source for command line tools is GitHub and DosTips. However, since the end of March, DosTips's certificate has unfortunately expired, which is of course immediately recognised and warned by all browsers. Not really a problem for me. I hope this will be fixed soon.
-
I have updated the YouTube files in the last XP-compatible PotPlayer version some days ago, taken from the most recent PotPlayer release. It works like a charm. No problems with cookies or anything else here. BTW, this last XP-compatible, slightly older PotPlayer is still the best media player under Windows XP, IMHO.
-
All is working here fine. Downloading, unzipping and so on. If you get a message "permission denied", then it is a limitation by your system for whatever reason. Maybe, by your security software or by some security policies. I don't know. I only can confirm that on a normal Windows XP installation, all commands executed by the scripts are working as intended. So, the problem is unfortunately on your side. Check your security settings! And here is a proof for what I said above: @Cixert As you can see, downloading and unzipping automatically by the script works like a charm. Please come and get your special treatment!
-
All is working fine here. Downloading, unzipping and so on. If you get a message "permission denied", then it is a limitation by your system for whatever reason. Maybe, by your security software or by some security policies. I don't know. I only can confirm that on a normal Windows XP installation, all commands executed by the scripts are working as intended. So, the problem is unfortunately on your side. Check your security settings!