Leaderboard

@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?

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.

maybe it is time that someone look the published codes from microsoft for example the WRK so we could tell why i had left open my fault saying 4 times 512 = 4 k, but that isnt right - it is 8 times however only cixert fixed that one up if FAT32ex on xp can acseed that 2 TB limit and set a sector size, it might be possible if not its not hard to write a loop that actually parse 512 bytes 8 times on the other hand it would raise question to that classical saying "32 bit are limited to 4 gb" according to this logic 32 bit cant address a HDD bigger then 4 gb the overlappend structure just use two dwords (aka 32 bit * 2 = 64 bits) (it has to be mentioned because in windows thats the structure windows use for file offsets) if i continue to talk like this i can only make speculations but lets say it would be able to pass the size of a dword (32 bits) it would not mean that it can pass the 512 sector as we know it can make 512 sectors with 4 gb (aka 2 tb data) but such things you can read out of the microsoft code/either disassembled/debugged or the published code - it is certainly some work - if someone actually know what the problem is it would be faster then just gambling around i actually wrote data to the disc on i/o level but that memory is far to old to get it back, it actually lack like the most part of it, i just remember a few I/O ports like 1f4 and the writes they are either dword (32 bit) word (16 bit) byte (8 bit) this is not a problem as you just give it a loop to write if you have lets say 1024 bits to write you use for the 32 bit writes (1024/32 = downrounded 33 times) 33 * 32 = 1000 then you still have to write 24 bytes , you can either do this with 8 bit writes or one 16 bit write and one 8 bit write 24 / 16 = 1 after that you have the last byte 8 / 8 = 1 = 1024 bits have been written the hardware actually transfer that code into a "next code" this next code dont really care if it was 33 + 1 + 1 writes, it rather finds the data that wants to be progressed (cache should be a a word here) to get this information out you need time it took 2 weeks just to compile chrome up another 2 weeks for getting the things around that that makes at least 4 weeks to dig into this - what time i dont have at the moment sorry maybe thats the right spot ? it definatly has low and high parts https://wiki.osdev.org/ATA_PIO_Mode#Registers quote: ";ATA PI0 33bit singletasking disk read function (up to 64K sectors, using 48bit mode)" quote2: "Note on the "magic bits" sent to port 0x1f6: Bit 6 (value = 0x40) is the LBA bit. This must be set for either LBA28 or LBA48 transfers." quote3: " An example: outb (0x1F2, bytecount/512 = sectorcount) outb (0x1F3, Sector Number -- the S in CHS) outb (0x1F4, Cylinder Low Byte) outb (0x1F5, Cylinder High Byte) " it is written in assembly to me it seems to have 3 words (word = 16 bit) that address a 48 bit offset (aka LBA48 / 16+16+16=48 (it seems low, mid and high/LBAlo, LBAmid, and LBAhi) the logic says it begins with a port that then counts up, it also says this port useally is 0x1F0 (if not its just that "beginning port" + X) (+3 / 1F3) LBAlo - 8-bit / 16-bit (LBA 48 are 16 bit) 8 bit is only for LBA 28 (+4 / 1F4) LBAmid - 8-bit / 16-bit (LBA 48 are 16 bit) 8 bit is only for LBA 28 (+5 / 1F5) LBAhi - 8-bit / 16-bit (LBA 48 are 16 bit) 8 bit is only for LBA 28 that again makes 48 bits, it is not a wire/address or 64 bit question you tell the device that 48 bits in 3 steps ... where you want to write - therefore it dont need a 64 bit address question - together they are 48 bit´s or just LBA48 after that you just write at that spot ... there is no offset - the "offset" has been set before --- if it is like that it isnt hard either you probaly have to set the right settings and address the 48 bits, its different from the paging mechanism (for ram) what actually has 4k pages, 4 megabyte pages, maybe segments, 64 bit PTE/PDE entrys (that can be done on a 32 bit OS, one example is that CMPXCHG8B command in 32 bit mode it can set 64 bit at once (atomic) ) another atmoic way to store 64 bit in 32 bit mode would would be to use the FPU unit the FPU unit can store 64 bits in an offset - to do so you could just put the two 32 bit values to an offset and storing those on the FPU , from the FPU you then store that value to the requied offset (aka where the PTE´s and PDE´s are at), in short talk you can use the FPU as integer if you do it rightm or even "just as memory storage for more then 32 bit" to make it via fpu unit FST / FSTP would be an example the opcodes (these are the ones who have a memory location, could be used) DD /2 (FST), or DD / 3 (FSTP) can write 64 bits to an offset: https://tizee.github.io/x86_ref_book_web/instruction/fst_fstp.html cmpxchg8b: https://www.felixcloutier.com/x86/cmpxchg8b:cmpxchg8b but jumping around from one project to a other just kills not only 1 project it kills both of projects, you guys are on the point

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

StartAllBack 3.9.8

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.

Use search, find this video. Translate the description from Bulgarian, you will see no acceleration will ever work in Pascal 1000 series. Add ten bucks, buy a 1070 instead of the garbage 1050, if you're willing to try, 'cause 1050 will simply BSOD on you. The driver WITHOUT H/W acceleration is in the video. https://www.youtube.com/watch?v=KwTvvQ3MuDk

@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 did not list them since they are more or less all similar to Allavsoft Video Downloader Converter.

@mjd79have your ever tried --memory-pressure-off ?

So! It's basically Ungoogled, right? No more need to apply patches @NotHereToPlayGames asked you to apply for him several posts before?

Rowl https://www.definitions.net/definition/rowl

Yes, a good suggestion to block rumour spreaders.

It would be odd to simply publish all of the source code of something which has *subscription mode* and paid Patreon versions, yes, I'm aware about the free github versions, too.

There was a leak, my first release wasn't protected with X-prot, so someone, someone I shared my app with, had hacked it and made another launcher app based on my knowledge, but it's nowhere near as good as the original, that person didn't know all secrets. Clearer now?

--disable-highres-timer speeds up considerably.

Not true, it's present even in older Supermium versions, not only the latest. You don't even need update to the latest hotfix 122 of Supermium. Try this. Paste and click enter. chrome://flags/#disable-search-engine-collection

Alan

Probably @Cixert assumed, and rightfully so, the double engine of 360 Explorer or something similar would be implemented in Supermium, too.

Akin

In case anyone has trouble reading through this thread, I can provide this bit of information. Using Dell Optiplex 9020, the LAN HwID is VEN_8086&DEV_153A The driver located in ProEMbSw11.exe in the PRO1000\WinXP Related\PCIe works just using manual update through Device Manager without having to do any file modification. Fortunately, it appears this file is in Archive from when it used to exist on Intel's website: https://web.archive.org/web/20181201110458/http://downloadmirror.intel.com/22928/eng/PROEmbSw11.exe

https://web.archive.org/web/20051227075035/http://wittswallpapers.com/Oldies/displayset.zip This is actually the Wayback Machine of a link originally posted by cannie. jaclaz