Leaderboard

Unfortunately I haven't been able to finish my hotfix, as I can't find the MSCF.sfx needed to finish it and I'm having issues trying to get it to install on a Windows 2000 system (no XP x86 for me). So, instead of making something with unredistributable M$ files, I just consolidated the changes into one reg file that works not only on XP, but all NT 5.x OSes (a little tweaking will bring it to 9x). I just applied it and it works - now Morocco is at UTC +1 and in Standard Time. The tzchange.dll and exe seem to be unnecessary bloat. https://mega.nz/file/B8MHwCrY#NJ9h0hroSch6eS6MhebpY7oGKIrx3OtzcWuPcoui-9U

Please download StartIsBack only from official sources.

StartIsBack++ 2.9.1

Server 2008 is the obvious choice being closer to XP. All this update does is update tzres.dll (Time Zone Resources), but that file doesn't exist in XP. What I see in 2000/XP is tzchange.dll and tzchange.exe, which can be used to modify time zones, and OS updates seem to use this tool to modify them as well (9x uses timezone.dll and timezone.exe). We should compare with XP timezone updates. If done correctly, we will have a Server 2008 update backported to XP, 2000 and 9x! (XP's DST update was backported to 9x) Thing is that these omniglot NT6 updates are confusing. Anyone know of a tool to properly extract them on my NT5 machine? Forget some of that noise, actually. All we need to do is write an INF specifying the timezone changes (as listed in the support article), I believe, in the same format as an official XP timezone update. No need to go into 2008 updates. OK, so the changes can be summed up as: Brazil no longer has DST, affects E. South America Standard Time and Central Brazilian Standard Time Morocco Standard Time fixed, changed from UTC +02 to UTC +01 Now how to express that in hex... The reg entries that would need to be changed would be in HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones, specifically Central Brazilian Standard Time and E. South America Standard Time. Under each is a "Dynamic DST" key with listings of DST dates (in hex) from 2004 to 2040, which means presumably Windows XP will stop changing from ST to DT after 2040. I think we can just delete the Dynamic DST entry for Central Brazillian and E. SA time because Saskatchewan time has no DST and no such entry, and simply modify the main key for Morocco Standard Time (which is somehow, still UTC 0 on my XP).

Yah... it'd be nice if Microsoft brought back full Aero. I find the win10 operating system works well enough, but aestically it felt like it went backwards. Without aeroglass it looks more like old school windows to me. Very boxed corners and no transparency. Like win98 or winMe kind of thing. It's shame MS keeps messing with the code and breaking aeroglass. If they stopped doing that, and figured out how to stop icons and windows from moving all over the place when you turn monitors on/off... it'd be a great OS

Hi @roytam1! I'd just like to say thank you for providing us with the IA-32 UXP builds! These older Athlon / Pentium III machines are still very useful, especially during this time of economic uncertainty, as some are being forced back into service for the less fortunate.

this Windows update has been auto installed itself on my computer three times already. I always uninstalled it afterwards. Before the third time, I left it on the computer for a couple of days, maybe I can get used to it. I couldn't. Not just because Metro surface lacks the aesthetics of Win7 Aero, but it has practical disadvantages too: the application windows has no visible borders which can be grabbed for resizing or moving. It's like MS has forgot the meaning of the name of their operating system, and thinks everybody uses all windows in full screen every time... So now I uninstalled the update for the third time and disabled the updates for as long as I could. Is it stupid to postpone essential updates for the sake of looks? Probably it is. But right now this is how it is.

Ah funny how small the world is, I didn't think you would be using AG too! And yeah no matter how long it takes, I'm always grateful about any update BigMuscle gives us.

Yes, that's me :P. And fair enough. I hope the person who makes this has time soon. World is in chaos now and I'm suspecting that he/she is rather busy with things at the moment.

I did the opposite. I uninstalled the update and extended my windows update installs deferment to late may.

Same issue on the MacBook trying to use VMWare. Problem was in sharing the computer hardware, just was too slow with the two OSs running at the same time. A solution was to use Apple BootCamp which transfers all hardware from one OS to the other. However, had to install Win 7 first in BootCamp and then update to Win 10 (MacBook is 12 years Old). BootCamp is now running Win 10 Pro, 1909, 18363.815. BootCamp Win10 runs faster than PC Win 10 in my experience.

I found a way for MIDI communication between the Win98 guest system in the MS VPC 2007 virtual machine and the MIDI music keyboard via the WinXP SP2 x86 host system: We connect the MIDI In port on our instrument to the MIDI Out port on the PC. Actions on WinXP Host: we install Virtual Serial Port Kit (FabulaTech) and add a pair of COM3, COM4 ports on the default settings: we install Roland Serial MIDI Driver 3.2 for WinXP and set the COM3 port in it, disable Use multiple ports and enable the Activate CTS/RTS Flow Control option: we install the Bome's Mouse Keyboard program, set the MIDI ports IN and OUT and leave the program turned on: set MIDI In to Roland Serial MIDI Input set MIDI Out to output port MIDI e.g. my Creative PCI card has this port Creative Sound Blaster MPU-401 Instead of Bome's, you can use another program that has MIDI In and MIDI Out settings, e.g. MIDI-OX in the Win98 virtual machine options in the COM1 port settings we select COM4: Actions on Win98 Guest: we install the same Serial MIDI driver but Win9x version - Roland Serial MIDI Driver 3.2 for Win9x and configure the same as on WinXP but set COM1 port: in the Control Panel Win98 set the default MIDI Roland Serial MIDI Out A device and/or use a MIDI player/sequencer in which you can select this port directly, e.g. Cubase, Winamp

April 2020 Updates: KB4550951 -- Security Monthly Quality Rollup for Windows Server 2008 https://www.catalog.update.microsoft.com/Search.aspx?q=KB4550951 KB4550957 -- Security Only Quality Update for Windows Server 2008 https://www.catalog.update.microsoft.com/Search.aspx?q=KB4550957 KB4550737 -- Servicing Stack Update for Windows Server 2008 https://www.catalog.update.microsoft.com/Search.aspx?q=KB4550737 KB4550905 -- Cumulative security update for Internet Explorer: April 14, 2020 https://www.catalog.update.microsoft.com/Search.aspx?q=KB4550905