jaclaz

@JorgeA Here is an adjective : crappy feel free to insert it between "another" and "tool" or between "disable" and "GWX", personally I added it in both places to be on the safe side while reading. jaclaz

Likely it won't work :unsure:. Nothing against VMWare fusion, but historically VmWare (virtual) hardware needs specific drivers whilst Qemu virtual hardware is "as legacy" (in the sense of "good ol' plain") as possible. Usually the first issue with an install/migration is the (lack of) basic "Standard Dual Channel PCI IDE controller" (I believe that VmWare uses LSI logic virtual controllers). For XP and 2003 there is Fixide: https://www.foolis***.com/free-tech-tools/fixide/ but I cannot remember a similar simple tool for 2k. Of course the above only makes sense if the Mac BIOS (or whatever) has a "IDE compatibility mode" or similar. jaclaz

Sure, MBR of course. XP doesn't really support GPT disks anyway (only 64 bit version has some support). Yep, making a 2k install in a Qemu virtual machine (I am saying explicitly Qemu and more specifically good ol' Qemu Manager) will create a "generic enough" Windows 2K install. Then a "changing motherboard" *like* routine might work: http://www.michaelstevenstech.com/moving_xp.html Whether this will work (or work better than setup) is to be seen of course, in any case I would try a "install from hard disk" (as opposed to "install from CD/iso"). Just in case Qemu Manager should still be available through Wayback Machine: http://web.archive.org/web/20120607071209/http://www.davereyn.co.uk/download.htm http://web.archive.org/web/20120506095037/http://www.davereyn.co.uk/qem/setupqemuk70.exe But right now they are having some form of misconfiguration and when the "original" site times out, the Archive.org seemingly assumes that there is a robots.txt preventing the archiving (which is of course not true, the links above were tested). Find it here: https://wohlnet.ru/soft/Virtualisation/QEMU/ https://wohlnet.ru/soft/Virtualisation/QEMU/setupqemuk70.exe jaclaz

The actual issue is not at all about the apologizing, it is about the interrupting. jaclaz

Yep, though the issue is of course about the actual hardware and the existence of suitable Win2k (or backported XP) drivers for it. The single/multi processor might be solved(actually worked around) with an installation with multiple HAL's/Kernel's to choose from in BOOT.INI. Personally I would attempt first an XP install, and only later attempt a 2k (if the first is successful) but possibly I would rather try a "base" or "universal" generic image of the 2K. While it is true that with this latter approach you will likely have more issues with device drivers, this way you would by-pass possible issues (limitations) of the Setup program. I recall that in the good ol'days - as an example - it wasn't possible to install 2k in Qemu and there was later a "hack" developed to allow it. jaclaz

Someone (reportedly) did it: https://macosx.com/threads/boot-camp-windows-2000.291782/ This is documented (Mac Mini though): https://web.archive.org/web/20060901003632/http://forum.onmac.net/showthread.php?t=1096 http://intelmacminiw2k.blog64.fc2.com/blog-entry-1.html#more jaclaz

Sorry to interrupt, but this is important. https://support.microsoft.com/en-us/kb/3173040 https://www.theguardian.com/technology/2016/jul/04/microsoft-windows-10-full-screen-upgrade-notification-pop-up-reminder jaclaz

Well, I would guess that it depends on what exactly you posted, maybe you overdid it or posted something like : I don't remember to have ever seen this three posts rule, maybe it is an anti-spamming precaution for new members . Yep, and more generally whining on another board won't help much. jaclaz

A protocol is not a server/service. Hint #1: 1) Disable/stop IIS 2) try sending and receiving an e-mail through Outlook Express. 3) Does it work? Hint #2 (historical note): Millions, maybe billions devices have been running XP WITHOUT IIS for years and still they managed and still manage to have SMTP mail (through Outlook Express or other mail program) working nicely. Final hint: You open the mail account(s) on Outlook Express and check what is in the SMTP server field. If it is a local IP, then you have a configured local SMTP server (which might or might not be based on that IIS instance), if you have a non-local IP address (rare) or more likely a web server address such as (example) mail.authsmtp.com you are NOT using IIS SMTP (virtual) servers and you don't §@ç#ing need them (in any case they are not working anyway). You have smtp.verizon.net (on port 465). Do you believe it to be local or belonging to Mr.Verizon ? Do you believe that shutting down a (non working) local virtual server that your Outlook Express does NOT use will affect e-mail sending or receiving capabilities? jaclaz

No. Your "normal" Outlook Express will likely need the SMTP protocol which has nothing to do with IIS or SMTP virtual servers. https://en.wikipedia.org/wiki/Simple_Mail_Transfer_Protocol Check the SMTP server in the Outlook Express account(s) you are using, likely it is a server provided by your e-mail account provider (i.e. your ISP or some other third party server). You are running (without knowing actually "why", thus I presume by mistake) an Internet Server, and this is evidently mis-configured. Those SMTP virtual servers are (clearly) not working since they cannot be even logged into, so *whatever* they are supposed to be doing, they are currently NOT doing it, since you didn't provide reports of any other issues (like mail not being received or delivered) it is clear enough that they have no use on your system. You have IMNSHO two alternatives: 1) stop running senselessly that IIS instance. 2) learn how to configure it properly, and then run it without any need or use for it. jaclaz

Ah, well, if you remove it from you XP Jumbo DVD using nlite, then it is not needed. @glnz Try following the given suggestions. Resetting/restarting the IIS should replicate the issue.. If - as expected - the issue is related to a badly configured IIS, the events will happen on restart. In any case there must be something in your task scheduler (or somewhere else) making it happen at that time. The data from the W3SVC logs is enough to know WHAT creates the issue, there is no need to netstat anymore, what needs to be understood is WHY this happens, and prevent it from happening, and again netstat won' tbe of any use for this, while resetting and reconfiguring IIS (or disabling it since you don't use it) and checking scheduled tasks is what you should do (that is if you want to solve the issue). And of course the shoes have nothing to do with this, the umbrella may. jaclaz

It is NOT a botnet, it is NOT a NSA backdoor, it is a misconfigured IIS attempting to start. Really Dibya, you should not post this kind of FUD. jaclaz

D@mn, I was hoping to be able to get some nice cups of coffee for free jaclaz

It is probably not the 64 Mb of total memory it is the "real DOS" memory, like the 640 Kb or the 1 Mb: https://en.wikipedia.org/wiki/DOS_memory_management Use another volume, have less files per volume, or as suggested earlier try with another filemanager, but I doubt that it will solve the issue with so many files and directories. What you report here: http://www.vogons.org/viewtopic.php?f=7&t=37021&start=20#p456296 however will need some clarifications, DOS 6.22 does not support FAT32. jaclaz

Should the app also make some coffee? In case, it should be black, strong and with two cups of sugar for me, thanks. Just to understand the theory, if (and when) such a program will be written, what would be the intended use of it? jaclaz

I am more dissatisfied with the: "Over 300 million people have already upgraded" As always meaningless (and very far from being reliable/credible) https://blogs.windows.com/windowsexperience/2016/05/05/windows-10-now-on-300-million-active-devices-free-upgrade-offer-to-end-soon/ is 300 million the WHOLE Windows 10 installs or just those that upgraded? Or in some two months since May 2016 hoards (literally) of people upgraded, tricked by the previous sneaky approach? The growth rate has been evidently (from the data available): https://www.thurrott.com/windows/windows-10/65759/build-2016-now-270-million-active-windows-10-devices around 34 million/month increase (whole install base), 8 months * 34= 272 =~ 270 million until 30 March 2016, then since 1st April to 5 May 2016 (roughly one month) it went up again to around 30 million/month increase. To be picky (as I am), in January it was (reportedly): https://blogs.windows.com/windowsexperience/2016/01/04/windows-10-now-active-on-over-200-million-devices/ already 200 million, so the rate is 70 million in roughly three months, i.e. around 23 million/month in the first three months of 2016. And earlier than that it was 110 million in October: http://www.windowscentral.com/windows-10-officially-installed-over-110-million-devices-over-125-billion-visits-windows-stor So: August 2015-September 2015 2 months x 55 million/month=110 October 2015-December 2015 3 months x 30 million/month=90 January 2016-March 2016 3 months x 23 million month = 70 April 2016 1 months x 30 million month= 30 Not really a "growing trend", rather an initial spike then stabilizing to arounf 25-30 million/month. Now how many devices might have been sold with Windows 10 pre-installed (not "upgraded") since August 2015? I would guess tens of millions, that should be detracted from the "whole" 300 millions reported in early May 2016, unless all those machines had been "downgraded" to an earlier MS OS or installed a different OS, and I doubt that all those devices could be compensated by "upgrades" in May and June.... To be fair, there may be a lot of people (like many members here) that did upgrade (to get the free license) and then promptly re-imaged the previous Windows 7 or 8/8.1, but I doubt that they are millions... jaclaz

Well, you would have tricked that young, naive, but otherwise intelligent person into taking a path without warning him/her of what lies ahead of him/her before reaching the expected destination. Not that much different from what Microsoft did when they put together the trap in which you fell. Omitting information or making it not clear enough. If at the time you got that MCE add-on license they had clearly told that the key had to be activated within (say) 6 months (or before January 2013) would you have attempted to install the add-on? Or if they had told you that there was no uninstall feature and you'd betteer make a backup before attempting the install? More information means more informed choices. But I will give you maybe a better example. From where I live to Florence there are two main roads, the first is going through a (toll) highway, and in about 15-20 minutes you get to the North area of the city, then from the North to the center it takes - it depends on traffic - 15-30 minutes more. The second goes through a (panoramic) road, some 10 km longer, and in about 40-45 minutes - regardless of traffic - you get to the center of the city. With these informations you can choose, if you are lucky with traffic the first one is a little faster, easier to drive but you have to pay a small toll, and once into town navigation is more difficult, the second is a little longer, it takes maybe 10 minutes more, but is free and very beautiful and while more difficult to drive it is much easier to follow. jaclaz

I am not protecting the world from your windows advice. I am protecting your windows advice from the risk of being misunderstood by the rest of the world. And sure you are not the only one, there are quite a few members that shared nice tweaks for the one or the other OS in order to make it better. Your statement taken without being familiar with the forum and your (and other members' and non members') contributions is what actually sounds not giving yourself (and the other members) enough credit (like none at all), while my nitpicking at least provided links to a (partial) list of the work by you (and other people) that made your OS so good. jaclaz

Well. the good news is that - as expected - noone is attempting to hack you. Those are seemingly created by IIS attempting to start. IIS has a long story of being particularly picky with a number of access rules (or permissions), if you google for that you will find tens of similar reports . What those (internal/local) IP correspond to on your network? 192.168.1.10 192.168.56.1 The two sets of message having a different timestamp may be because one is UTF/GMT and one is "local time": Event Type: Warning Event Source: W3SVC Event Category: None Event ID: 100 Date: 6/28/2016 Time: 5:30:13 PM #Software: Microsoft Internet Information Services 5.1 #Version: 1.0 #Date: 2016-06-28 21:30:13 21-17=4 hours, if you are on the East Coast of the US (say New York) that would be accurate. You may want to try resetting the IIS manually: https://msdn.microsoft.com/en-us/library/bb742502.aspx very likely it will produce the same "set" of entries in the various logs. jaclaz

Actually both. Without knowing you, your statement seems like a full endorsement of "stock" Windows 8.1: we know that it is not the case. Without context this could provoke two kind of reactions: 1. people may think that you are one among the blindfolded MS fanboys (and thus I am protecting you from this possible mis-characterization) 2. people may think that your enthusiastic endorsement, since it comes from an experienced user is accurate and reliable and might decide to follow it (but without the tweaks/addons/fine-tuning) and they will find themselves with an awful looking, much less productive that a "stock" Windows 7 OS. (thus I am protecting them) Once they know that with some work 8.1 can be turned into a more than decent OS, comparable with Windows 7 (with which presumably they are already familiar), they will be correctly informed. jaclaz

https://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Windows+Operating+System&ProdVer=5.2&EvtID=4226&EvtSrc=Tcpip&LCID=1033 Try running netstat -o or netstat -p TCP -o, the "periodical" (once every 24 h or so) nature of the issue may actually be connected to *something* in scheduled tasks, it is well possible that *something else* is stuck (keeping a number of open connections) and that when a process starts (every 24 h) it maxes out number of connections because there is a permanent high level "ground noise". The recorded attempts for Administrator, administrator, Admin and admin don't sound that good, but not necessarily they mean an hacking attempt, similar Warnings can be generated by "normal" services in case of issues with folder/file permissions try checking (if there is one) the files in: \system32\LogFiles\W3SVC??? A hacking attempt with a few attempts every 24 h doesn't seem really-really a "hacking attempt" (or the hacker is VERY patient ) jaclaz

Well, (at least this is what I do personally when monitoring an address for a test) normally one inserts a timeout so that there is no more than a ping per minute or so, in this case having a 40 seconds interval between pinging the same host sounds just about right to me. To each its own of course, personally (of course it depends on the specific case) I notice a lot of people usually asking for (polling and receiving) much more data than what they actually *need* just because they can.[1] But nothing prevents to have - say - four command prompts open, each pinging a subset of 10 addresses. Anyway the Nirsoft little thingy you linked to seems just about right for the core jaclaz [1] I mean, say that you ping every second each host. Suddenly one out of the forty fails the ping. How long is your "reaction time"? Nanoseconds, milliseconds, second or minutes? How long it take the "intended remedy"? As an example rebooting a device or PC? Nanoseconds, milliseconds, second or minutes?

I had a saying for that, that I cannot remember right now, but that essentially means "that ain't be cheap": http://www.whatsupgold.com/buy/global/index.aspx € 1,727 per year for 25 "points", and OP would need the 100 "points" version for a mere 2,484 €. Sure the trial version could be used (if it will be used at the most for 6 hours), but (haven't checked) most probably it also has a number of hosts limit. Now I remember, that saying, it was "as expensive as the cannon needed to shoot at flies". Seriously now, a simple script for pinging a few hosts might be more suited . Something more or less along the lines of: Unfortunately most of the snippets posted have been corrupted by the last (or maybe the one before the last) board update. This (basically) would do: @ECHO OFF SETLOCAL ENABLEEXTENSIONS :Endless_loop FOR %%A IN ( 192.168.0.1 10.2.7.5 8.8.8.8 ) DO ( ECHO Pinging %%A PING -n 1 %%A|FIND "TTL"||ECHO.&&ECHO %%A NOT Reachable&&ECHO. ) GOTO :Endless_loop One might insert a delay before the GOTO to slow it down, so that it pings the list of targets every x seconds or minutes. jaclaz

I will have to repeat the needed disambiguation for the casual onlooker. What NoelC finds "the best Windows OS" is NOT "Windows 8.1", it is Windows 8.1 BUT ONLY after having been accurately tweaked and tuned, with a number of third party add ons (related to GUI/Shell) and numberless tweaks implemented by himself, i.e. basically completely unlike what the "average user" receives from MS. See more details here (and following): And here: jaclaz

Strangely enough, some good news ;): http://www.seattletimes.com/business/microsoft/microsoft-draws-flak-for-pushing-windows-10-on-pc-users/ jaclaz