Leaderboard

Hello.. I created an account here to thank you for this awesome browser! Used PM years ago (stopped when they dropped support for xp) and stumbled upon this place just a few days ago and glad I did! Working quite well so far! Take good care everyone and glad to be a member of the forum :)

Unfortunately on this specific topic, and notwithstanding the carelessness with which the good MS guys manage the information, they are not entirely wrong. 32 GB is an artificial limit, and was imposed when RAM availability actually meant something, but it is not a very good idea to go for large FAT32 filesystems, unless there are very good reasons for them. 64 GB? Ok. 128 GB? Ok. 256 GB? Hmmm. More than that? Naaah. jaclaz

Never mind. It's a matter of opinion. I don't think the features mentioned in the link I posted are bells and whistles. They're all sorts of important improvements.

New build of Firfox 45ESR SSE: test binary: https://o.rthost.cf/gpc/files1.rt/firefox-45.9.10-20180721-11012c83f-win32-sse.7z repo: https://github.com/roytam1/mozilla45esr Changes since my last build: - import changes from tenfourfox: - M1256520 + M1248314 (027a6309b) (d40656c0f) - NSS: applied Bug 1474875, Typo in policy handling for DTLS-VERSION-MAX, r=ueno (99462bf91) - import changes from tenfourfox: - #512: modified M1222924 (c59480e6b) (68313f3d2) - import changes from tenfourfox: - #512: update EV roots (b6afdab5d) (only EV part is merged here) - remove annoying warnings from IOService, since we support old extensions (2f6fe15d3) - Fix regression from #511 (#515) (1ec366235) - #334: remove tele from security/manager/ssl (5cf00f4a2) (28c3c4354) - import changes from tenfourfox: - #512: M1472018 M1469309 M1472925 M1470260 (part 1) (f9fe116fa) - #463: fix name of pref II (05241abca) (11012c83f)

I've decided to put it online for awhile after all, figuring that nobody will probably notice. http://209.65.198.189/ I've created an index page listing the sites, so all you have to do is click the link to the one you want to visit. Many of the download pages in dosghost are still broken, as the filenames of the download pages got mangled somehow (why this didn't happen to any of the others, I don't know), but I plan to fix them. As for the server, using EZ-NOS 2 on top of MS-DOS 6.22, all running in a VM (for added authenticity). This is probably why the download page filenames got mangled (no LFN support). Enjoy! c

Thank you BigMuscle... working just fine so far. Keep it up and thanks again.

The off-line windows 32-bit installer (file jre-8u181-windows-i586.exe) continues to function properly on this old Vista SP2 32-bit laptop; I suppose this is of no consolation to XP users of this thread, just reporting it as a FYI here; the GUI during installation (which itself took quite long, ca. 5min on this old, under-resourced, machine) was slightly redesigned to be of a more elongated rectangular shape; but it did include a link to the following Oracle article: Release Notice a message the XP users are unlikely to see, due to the installer being broken on that OS Regards

Or maybe he understood it all right but found it "not funny" (IMHO it is not only "not funny", but also confusing to many members). jaclaz

Try just this from a dos box before anything. I've used it many times in the past. It just works. %systemroot%\Microsoft.NET\Framework\v4.0.30319\ngen.exe executequeueditems

I can't say, Jody. I would suggest that either holding back at (I believe) the December 2017 level or bringing your system fully up to date are the most viable alternatives. Based on what I've read some of the Meltdown mitigations changed the entire way the operating system is built from sources, so I don't think this is a mix/match type of situation. I have always kept my critical systems up to date, and have been blessed or lucky to have good, stable operation, but a best case slowdown equivalent to the difference between my computer and one I could have bought for $1,000 less was simply something I couldn't accept. I wish I could say there was a margin for error here, but I've been through the trial of the latest updates in Win 8.1 not once but twice, (and also with a Windows 7 system) and I really, really measured carefully. -Noel P.S., in response to dencorso's note, I found this nice post which identifies the DISM command that can be helpful for removing historically layered telemetry updates: https://www.askwoody.com/2016/how-to-permanently-remove-kb2952664-and-maybe-speed-up-your-machine-in-the-proceess/