Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

All Activity

This stream auto-updates     

  1. Past hour
  2. I am using roytam1's great browser builds and I am always wondering, why are they running so slow when using XP. The same browser build used with Win 7 (32 or 64 Bit) runs much much faster. Ads are not the problem, neither is the agent string used. Even if there is nothing I can do about it, I am interested in the reason. Here is one site which is free of ads and shows up pretty quickly in Windows 7 with roytam1's KM-Goanna, Basilisk and PalemoonXP, but won't even load completely in Windows XP: https://www.binance.com/de/trade/BTC_USDT PS: No discussion about crypto's please.
  3. Yes it does. Personally, I think if the broadcasters mandate DRM (as appears likely at this point) it will merely ensure the new standard never becomes the dominant one. DRM would require anyone selling a 3.0 tuner to figuratively sign their business's life away to get a key. Only the biggest TV manufacturers (Samsung, LG, etc.) will be able to afford to do so. TiVo will be the only DVR maker that can do so. SiliconDust, maybe (they managed it for CableCard access), but you can forget about any $40 3.0 tuners, as the 1.0 world now enjoys. And of course the tuners would have to use HDCP, so say goodbye to component video; and the TiVo recordings would be encrypted, as they are for (some) cable recordings now (depending on what channels your cable provider flags with DRM). So we'd be paying more for equipment that does less. And for what? Higher resolutions than most folks can even see? "Interactivity" (which failed with ATSC 2.0)? At best, it sounds like ATSC 3.0 might become a niche market for videophiles, like HD Radio became for audiophiles. OTOH, maybe the broadcasters will force the issue, by (say) lowering ATSC 1.0 picture quality back down to SD and/or dropping some of the subchannels you've come to enjoy. You want to keep what you have now? Then you must "upgrade" (and put up with all the DRM restrictions).
  4. Today
  5. Just a guess on my part but Pale Moon/UXP support will probably continue on Windows 7 for as long as Mozilla supports it and by the looks of it that's going to be a while. 68esr is good until next September and then 78esr for another year unless they break it in the next four nightly versions, highly unlikely. Windows 7 is still being supported by Microsoft if you pay (or install a hack and get the updates for free) for three more years so it's going to be another POS Ready situation.
  6. Sigh .... no I'm not trying to get kudos of any kind, and my running Windows 8 was just for full disclosure that I personally had no fight in the game. So don't like my posts then. :(
  7. The legal way to get the POSReady '09 updates also required payment (for POSReady '09). I suppose a distinction could still be made: if the POSReady '09 XP hack wasn't published until after POSReady '09 was no longer available for sale, then the hack could be considered not stealing since you couldn't buy it from M$ anyway. But it does seem like a rather fine line we're not crossing. At any rate, perhaps a more acceptable route would be to do what POSReady '09 did: spoof a different Win 7 version, perhaps Server 2008 R2. It would be more challenging than the XP registry hack - I think you'd need to hook GetProductInfo, so it would require some programming - but sounds prima facie doable.
  8. ... Adding to what my friend @Vistapocalypse posted, MCP dropped Vista support in Pale Moon with the release of v28.0.0 on Aug 16th 2018, a mere 16 months after Vista's own EoS (end of Extended Support by vendor, which was Apr 11th 2017); so yes, XP diehards shouldn't be moaning over this... Would I have wanted official Vista support to have continued past Tycho (v27.x.x) (and that would've been at a minimal cost, considering how much similar Vista & 7 are, both NT6) ? Of course yes ... But when MCP started developing UXP (forked off FxESR 52, both XP/Vista compatible), Vista had already reached its EoS, so, in his own words, he didn't want to implement support for a "dead" OS in his "new" application platform... https://forum.palemoon.org/viewtopic.php?p=134148#p134148 Addition: In a now hidden () GitHub comment of mine, my own view on the matter: Just for the sake of clarity, Moonchild's response(s):
  9. Me thinks a Windows 8 user accusing Moonchild of hypocrisy in the XP forum seems like an easy way to gain kudos, and indeed TechnoRelic seems to have liked your posts, but I don't. Microsoft's EoL date for Windows XP was April 8, 2014. According to Pale Moon - Release Notes for Archived Versions, that was soon after version 24.4.2 was released. Did Moonchild "steadfastly" rid Pale Moon of Windows XP support by the end of the month? Absolutely not! Pale Moon 25 and 26 continued to support XP, and version 27.0.0 wasn't released until 2016-11-22 - more than 31 months after XP's EoL. If Moonchild ends support for Windows 7 before August 2022, then Windows 7 diehards would actually have something to gripe about - and btw support for Windows 8 might also end at such time...
  10. Doing a little research it seems Notepad++ 5.9.1 (ANSI) is the last version to support Windows 9x/ME as per user PeterJones on the Notepad++ community forum. you can find version 5.9.1 here be sure that you download the bin.zip or bin.7z version... the .exe installer only has the Unicode version which doesn't work on Win9x/ME.
  11. There's different ways of doing it and the -no-remote -Profile method is how I've done it with different thunderbird versions.. If you're using a portable on flash drive another way is to download a portable FF version then swap the App/firefox folder with a renamed basilisk. Works just as good and doesn't require a profile.ini either.
  12. You could also try petrus's suggestion: That idea should work with any FF-derived browser (NM, Serpent, Navigator, etc.)
  13. I haven't read the topic (registration required, and it's not a big enough deal to bother registering) so I'm just guessing that they're following Google's timeline for Chrome, rather than M$'s timeline for Win 7 itself: As to Win 8, it's interesting that it's newer than Win 7, but also hit EoS earlier (since everyone was "supposed" to upgrade to 8.1). So if/when they do stop supporting Win 7, they might just set the minimum required version to 8.1 and we'd all be out of luck. But it may also have to do with programming. Another guess of mine is, it's not really any harder to support Win 7/8 than it is to support 8.1. If so, MCP may not see much advantage in cutting off Win 7/8 support in terms of removing code from the product. The chance to remove code and make the browser package smaller seems to have been one of their motivations to drop XP support (less sure about Vista) back in the day. You were perfectly clear; that's why I said you probably wouldn't like my solution! FF 52 doesn't support SSUAOs (at least, not without considerable tweaking), so an extension like "Good Twitter" is needed to send Twitter a different UA (so their Web server will use the old interface). However, this also causes Twitter to send the audio that @roytam1's built-in support wouldn't have handled correctly, but since you're (of necessity) using Primetime with FF 52, it plays fine anyway. As for getting it to work in NM, his built-in support is probably getting the sampling rate wrong somehow. Unfortunately I don't think anyone yet knows quite how to fix it.
  14. The way I run it in portable mode is to rename the basilisk folder firefox and also basilisk.exe to firefox exe then swap that with the App/firefox folder. You can put your profile named "Profile" in the data folder. Edit: should have mentioned that this requires downloading the portable firefox version then swapping the renamed basilisk and basilisk.exe with the portable firefox version: https://sourceforge.net/projects/portableapps/files/Mozilla Firefox%2C Portable Ed./
  15. They probably figure since they're doing the work to maintain it the inconsistency is just fine. Google, Microsoft, and Mozilla can be just as inconsistent at times and they will always find ways to justify it. On Windows 7 I'm using this version since it restores many of the features they've removed so either way I'm glad the support is still there and hope it doesn't go away anytime soon.
  16. Hi How do i run this browser in portable mode? because everything i run this on a different computer, i've to set everything from scratch! Any command line context?
  17. You run the proxy on an XP or above host and then point your old machines to to it. The modified Firefox browsers I posted were intended for your Qemu test, not on host Windows 98. They can be found here: https://o.rths.ml/gpc/files1.rt/home.html For 2000 with BlackWingCat Extended Kernel Seamonkey 2.39 and 2.49.5 works
  18. VirtualBox 1.5.6 is the final version officially supported for vanilla Windows 2000, but VirtualBox 2.0.4 is the final version using a modified kernel driver made by BWC. But, if you use the extended kernel and core, you can use VirtualBox 4.1.22 (and possibly up to about 4.1.32 - 4.2 introduces driver incompatibilities). However, you must manually install the kernel/networking/USB drivers from the "drivers" folder in VirtualBox's program folder using the included infs. USB 2.0 passthrough seems to be broken, just like in 1.5.x.
  19. I guess we'll see how it is handled. This website indicates it is in ESU: https://support.microsoft.com/en-us/lifecycle/search?alpha=Windows Embedded Standard 7
  20. Well there is always a way. We'll see what the ATSC 3 tuners end up supporting. My guess would be that they would want to couple the DRM into the HDMI spec. Will we get set top tuners that will still have composite on them? Even my modern 1080p tuner still has a coax out on it. If the DRM ends up only on 4k content (and even so) it may not be an issue if you pass it through an AVR first. Only time will tell.
  21. Oh I agree that Matt's co-operation with the crew here is tremendous. I just hate when people are disingenuous in any manner.
  22. title.. Help can't find the option. got startisback++ 2.9
  23. (MAT) Mat A Tobin (PALEMOON affiliated programmer = Borealis Browser , more) is now supposedly supporting to contribute to BRANDING activity with regard to RT's Browsers (WinXP OS). But to be certain , for MAT , the goal is also to minimize annoyance to MAT (PALEMOON) too. Which actually , Mathwiz did PULLS to fix the HELP URLs active in the RT Browsers , to aim at RT websites. That was done via no prompting from MAT either. So , not sure what that means for MAT or PALEMOON. But , Mathwiz sees an upside to working with MAT on BRANDING of RT's Browsers , same here. As to IF that anything will actually come of it (RT BRANDING and MAT) , not sure. But at least there is a notion to listen to MAT. Rather than to freeze out MAT over past friction events. As to "flip-flopping" or even trolling (?) behavior based on "bugs me" , actually FINE here. JT replied below --> "Matt's co-operation with the crew here is tremendous." ... NOT quite sure what "crew" that you mean it. And RT (himself) seems somewhat underwhelmed by BRANDING notions , but okay. JT replied below --> "I just hate when people are disingenuous in any manner." ... The INTERNET is a big place.
  24. This has been a fun ride for me, and the SSL issue on Windows 95 seems to be officially solved.
  25. Also, SeaMonkey is the closest parent to Netscape (more so than Firefox), it even retains some of the old look. I basically loaded SM 2.49.5 with a custom netscape theme. New Moon 28.8.x also works here and with a Netscape theme as well. New Moon is a fork of firefox/pale moon with some differences between them. I prefer SM because its more closer to a “vanilla” solution even though it only runs thanks to BWC. So far SM was capable of doing everything except banking (I haven’t tried and never will).
  26. Very interesting that Moonchild is perfectly OK with continued use of Pale Moon on Windows 7, which is now EOL, but they couldn't be steadfast enough of ridding of Windows XP support. Now, I'm fine with the mass-jettison of XP, but it's either one way or the other. Me thinks, since the Pale Moon crew runs Windows 7, well then that makes it OK, but since XP is just all the rest of you, well too bad. I'm over on Windows 8 anyway, and again I'm not an XP defender, but flip-flopping on an issue just bugs me. https://forum.palemoon.org/viewtopic.php?f=66&t=23681
  27. I had no trouble with nForce3 chipset drivers, I had a DFI LANparty nForce3 motherboard which previous owner had damaged one IDE controller which was an issue but all else was fine. The IDE driver is easy to update to 2.0.950.3020 date 2003 from VIA. This driver has to be chosen as the 98/ME original driver will have a higher version number. Have all your nForce driver infs installed in the windows inf folder. I un-install ACPI and the PCI bus and then install PCI bus first manually. Then install drivers, take a look at what drivers are compatible and choose the nForce ones. Do not force any other driver unless they are shown as compatible. This means that there will be several standard PCI bridges installed. This will ensure the South Bridge PCI to ISA bridge is installed which is an ISA emulator otherwise this ISA emulator will mot be detected. The latest drivers from VIA for 98/ME are a good improvement especially the USB and IDE drivers. nForce chips are quality IMO but still can be destroyed, make sure all chips have enough heat-sinking. Getting old hardware that is not damaged would be a challenge, if your board is good then I would persevere with it. >Does anyone have experience with a tualatin and 440bx? 440BX was the first Intel chip to hit 100MHz but it just made it in some cases and the design was mostly an over-clocking approach to the BUS so AGP and PCI cards had to be very good to work. Tualatin's need 133 FSB speed and if an adapter is required I would choose a board that can handle 133MHz FSB natively not just over-clock.
  1. Load more activity
  • Create New...