j7n

Member
  • Content count

    342
  • Joined

  • Last visited

Community Reputation

16 Good

About j7n

  • Birthday January 13

Profile Information

  • OS
    XP Pro x86
  • Country

Recent Profile Visitors

1,323 profile views
  1. I thought everyone on this board knew what nLite was. It is a tool for customizing a new Windows installation image. One of the last steps consists of a long page of registry tweaks.
  2. I usually use the tweak set from nLite, which comes with brief descriptions, and some visual and functional tweaks such as classic theme for the system account of the shut down event tracker to get an extra safety prompt. But those do not affect performance directly. XP absolutely needs to have the networking settings tweaked for performance. I use a registry file for that, because it is quicker to just double-click it and be done with it, rather than drag sliders around in TCP Optimizer. No harm comes from settings that have no effect on the particular OS version. TCP-IP_Settings_for_Win2kXP2k3.reg
  3. Did you check if the profile size counter overflows at 4 GB on XP? A quick check of the screenshots on Google showed some where the profile was bigger, but those seemed to be from NT 6. It would be funny if Microsoft never meant for users to have more than 4 GB of My Documents, My Music and My Downloads. My system partition is 3 GB, so I can't do the experiement. Administrator directory is 339 MB (348 MB with cluster overhead), Local Settings is 83 MB, and Profile Size is 256 MB. Alacran has good advise. In addition to that, I would also move out the largest application caches and user's %temp% out of the system partition to avoid the file system on C: being slowed down by repeated creation of thousands of temporary files. Maybe Local Settings can be redirected entirely, but that probably has unforeseen consequences, because the data in that directiory is of variable pemanence. I've moved web browser caches out separately. This reduced the file count in the profile to 9100 (macromedia flash cookies, various application presets), which is mostly static unless I add or remove applications that add new files in there. I have a separate S: Swap partition of 2 GB (which apparently is a problem, because I encountered one modern program that attemted to allocate memory for a DVD's worth of files in Swap), and a T: Temp partition of 10 GB, which can be wiped entirely without lasting effect. Those two could go on the same volume. Mixing documents with system files always striked me as very odd, but apparently is now the right thing to do on Windows. Logically, only various "settings" which may or may not be part of the Registry, depending on the program, should be stored in that profile.
  4. On my systems, the Profile Size does not include the Local Settings subdirectory. This directory contains mostly discardable temporary caches of various applications, and also the save game of Need for Speed Underground 2, which is very much needed. I guess applications don't use these directories consistently, especially if Microsoft changes how they're supposed to be used with every new Windows version. You could move files into and out of the directory and bring up the profile dialog again, and see which files count. As far as I'm concerned, the total size after any manual cleanup matters if I want to transfer my settings to another computer. I suppose the current user registry ntuser.dat is over 1 MB on any system that has been in use at all. Since I use Total Commander daily, I do Ctrl-Shift-Enter to calculate directory sizes quickly, and then look at the largest ones. Not as readable as a graphical tool, but still helpful.
  5. I have disabled Web Fonts for some time in Opera 12 to avoid their download and visible refreshes of the page. Sometimes the fonts would remain loaded in the system after I closed the respective page. opera:config#UserPrefs|EnableWebfonts Problem is that many websites now have buttons and icons drawn using font glyphs. Those do not show correctly if I disable web fonts. Commonly the search icon becomes the ligature "fl". Most new downloadable fonts generally require ClearType to look good, with some exceptions. Here the absence of vertical anti-aliasing, breaks up some glyphs. If web fonts are disabled, the page falls back to a system font that is tweaked to look good with standard greyscale anti-aliasing, but the header no longer has an icon for the "user" and "basket" buttons.
  6. I agree with you. I use Opera daily, but avoid heavy javascript-based sites, such as the new MSFN. Windows 2000 or XP is probably just fine for a special purpose built computer, if parts that aren't essential for the application are shut off, such as file and printer sharing and web browser. With every new version, Windows has taken on more functionality, and of course security issues in every one of those components. Luna theme and with clouds and the green start button is a hard to imagine on a military ship...
  7. Surprisingly, I got a readable translation from Google Translate. "When you buy a ship, you do not buy it today, you bought it 20 years ago." I don't see why this can't apply to computers too. Big corporations just want us to throw old technology out and buy new for no reason. I'd replace the boot logo with one of the navy, put the classic theme on, and confuse the journalists into thinking it is Windows 2000.
  8. WinRAR 5.50 beta 4 (since a few versions ago) requires XP SP2, and fails with EncodePointer error on XP SP1, and with "not a valid win32 application" error on Windows 2000 because it demands subsystem Version 5.1. With that out of the way, Windows 2000 still complains about TzSpecificLocalTimeToSystemTime, and would probably get to uxtheme and EncodePointer eventually. If you have a patch for Windows 2000 that extends it so that XP programs run, then it is right to say that it runs on 2000+patchX, but not 2000 SP4 by itself. What is that update by the way? WinRAR does not require SP3. Programs that do, fail with GetLogicalProcessorInformation. I suppose MSIE is by design meant to run only on current versions of Windows. It is unfortunate that is integrated into the system so much, and, among other things, depends on SSL DLLs that the system uses for other purposes. Windows 10 will be very confusing when it comes to system requirements.
  9. I find this attraction to "death" of commercial products by neophiles quite silly and almost in poor taste. The MP3 format also just "died". Layer-2 and AC-3 are probably fossils then. These Youtubers and forum members are doing advertising for Microsoft without realizing it. Disco is dead! I wasn't going to make a post about it alone. But now that I'm here already. Why would you take driver files from Server 2003 and try to transplant them into XP to get more memory & bigger disks working, instead of starting with Server as a stable working base and building up from that?
  10. I future proofed myself and entered Firefox 77.0 in that field, and added few funny messages in the end of it. I'm still using Firefox 27, upgraded from 22 a short while ago, because common sites that have nothing to do with money insisted on TLS 1.2 support. I got no desire to research how to disable stuff in newer versions. The blur of "skia" was a total disaster on my mom's PC; I'm glad I found a solution on MSFN.
  11. Excuse the bump. I too strongly dislike ClearType. The tuning is to a large degree in the fonts, their hinting. Firefox's setting was to use cleartype for downloaded webfonts, and that is usually for the best, because they were designed recently assuming CT was on. But Тahoma and Verdana - Windows system and classic web fonts - do not work with it. If I choose dark type (the first squares in the tuner software), the font weight increases and characters in boldface text bleed together and have decreased readability. If I choose light type, bold menu items look acceptable, but regular text is too light and increasingly purple. Maybe this is why they replaced the system font with Segoe. ClearType also doesn't work on cheap flat screen with either narrow viewing angle (laptop / TN) or poor response time (PVA): if I sit close to such as screen or scroll text on it, vertical lines in glyphs will become distinctly purple and the color will vary across a line of text. These screens were the only types available when XP was released, and the system also didn't have any special fonts until Office 2007, and looked horrible. Also no anti-aliasing in the vertical direction. The letter O has top and bottom pixellated but not the sides.
  12. Maybe it is easier to get any common Ethernet card working in a Win98 computer and connect it with a cable to a Wlan router, which is configured in station/client mode to access the wireless network. This eliminates need for wi-fi-specific utilities that can be unstable or slow the system down.
  13. Has the PDF format been fundamentally changed that a new reader is required to view files made as of now? I don't think so. I use PDF-XChange Viewer 2.5, released in 2014. It is small enough, renders type at high quality, and has good UI design without flattness or ribbons.
  14. I have solved this issue after reading the experience of some users of VMware Tools and mIRC. https://communities.vmware.com/thread/513894?start=0 http://forums.mirc.com/ubbthreads.php/topics/241712/mIRC_7.27_and_7.29_causing_BSO I was surprised that both VMware and mIRC accepted reports about older OS as valid. Respect to them. The culprit turned out to be an overly complicated manifest resource: two "xmlns" values per any element, as well as a section <ms_compatibility:compatibility ... >. Removal of those stopped the crashes. Replacing <ms_compatibility...> with <compatibility><application><supportedOS ... also seemed to work. Copying sxs.dll 5.1.2600.2932 from the KB921337 hotfix into XP SP1 hasn't caused any new issues yet, and also allows software that previously crashed to work. Yes, I still have an installation of SP1 which is heavily cutomized. Getting all settings and applications installed again on a new OS would require much effort. <rant> I have always hated manifests and the winSxS system, because they don't allow to easily copy MSVC runtime DLLs. But I didn't think they would be the cause of crashes, the kind that just don't happen since Win9x. Supported OSs and whether XP themed controls should be enabled could be recorded in a few bits in some header, instead of a big file in text format that needs to be parsed, and contains impossible to remember GUIDs. I just googled sxs sucks or something similar, when I came up to the posts containing the solution. </rant> Long live XP.