ReactOS Milestone!

(WARNING: KIKETUBE LINK) https://www.youtube.com/watch?v=3YhOu5zKl04

ReactOS can now run Dev-C++, a IDE from the early 2000s that comes with an ancient version of MinGW, and can run the OpenGL example program that came with it! And now it even has a Windows Vista theme!

What a time to be alive. Maybe soon I can run my viruses and botnets without an NSA hijacking my computer and selling my information to Walt fucking Disney.

^{(Snark aside, it's a really neat project).}

That's fucking cool

fonts looks amazingly ugly

thanks for the trigger warning.

And now it even has a Windows Vista theme

Why would you want to do that? Windows Classic is superior.

>>5
Agreed. Nothing is more comfy than using Dev-C++ on windows XP.

the OP post is hilarious in how hard it tries to fit in

>>7
Try hard to fit in my anus.

Well, I was going to try making the first post from ReactOS, but I built the latest in the SVN repo, and iexplore.exe BSOD'd on me. Just opening the directory of Firefox crashed the whole system. Tor Browser couldn't connect to the control port over localhost. Reinstalled, now iexplore.exe starts up, but can only load http://www.reactos.org . Eventually freezes then crashes the system. Then I tried looking for something programming language to install. GHC was the first to get fucked, because it wants almost a gigabyte installed, and I had already only made the virtual disk 2GB. Fuck Haskell and that bloat. CLISP worked pretty well, except it would crash REPL if any key other than `(' was the first one pressed. Weird. Python, it turns out, had a 64bit version, so I didn't test it because I was too lazy to redownload it, so I'm failing it too. Strawberry Perl would exit immediately. Java SDK couldn't even begin. Froze every time I tried to install the VS2015 preview. Embodiment of the Scarlet Devil couldn't get DirectX to work.

Then I notice that I sure do seem to have a lack of disk space. Some interesting results in the `users' folder (why have both `users' and `Documents and Settings'?), including a folder from 00/34/8212 35154:64 PM and a 2GB file from 57/56/0044 32:48 PM. Needless to say, both are very strange dates.I'm displease that we will be start counting months from zero, but I'm glad that we have more days in a month. I do imagine that it will be tiresome measuring time with over thirty five thousands hours in a day though. I'm guessing the file from year 0044 has it's timestamp measured in moons? But what really concerns me is that FAT32 has a 32 bit timestamp, so I have no clue how this even happened. I don't even know what to say, really.
C:\users\Local Settings>dir
Volume in drive C has no label.
Volume Serial Number is CA0B-19F4

Directory of C:\users\Local Settings

02/13/2009 12:00 AM <DIR> u¬}║²q.Θ÷
07/14/1992 12:00 AM <DIR> ÷êöä]X╖j.⌐Ö╜
10/13/2036 12:00 AM <DIR> ╩;r∞αWì.sjq
çí.╚x0044 32:57 PM 2,371,902,458 d╦o5b
01/02/2020 04:58 AM <DIR> Γ│5QⁿÑ╘.▌&"
11/16/2083 02:22 AM <DIR> ?ì║tu▌÷.αná
05/14/2103 02:21 PM 2,908,613,686 σ¡üóσ.╕║é
01/20/2054 03:58 PM <DIR> )┘φk[.Üc
08/25/2101 12:00 AM 2,702,820,192 ﺠ&╘σ².Zª▀
09/30/1998 12:00 AM 1,457,854,770 \╙ë⌠£╧.╝tà
01/28/1981 12:00 AM <DIR> δ?u[┌ºô
10/27/2025 12:00 AM 2,755,428,536 ·ùΩpæ.é╝K
08/03/2089 08:31 PM <DIR> ▌ú'GܪSx.╨<*
12/26/2082 12:00 AM <DIR> ·d¬L}'æ.ñ≡
00/34/8212 35154:64 PM <DIR>  åù╘u╨n.v∙
05/25/2004 12:00 AM <DIR> #╣[∩uùπ┐.╟╞N
00/34/8212 35154:64 PM <DIR> u╛nè░ôu▌.ÿu 
12/21/2005 12:00 AM <DIR> ≤h│tƒ╓¥.ù┬╬
12/09/1997 06:10 PM <DIR> >QÅt╣╣wo.â&"
05/09/2099 12:25 PM 3,528,003,763 èd²░[¼╝t.±ƒ
48/57/0044 32:56 PM 1,029,888,374 -t\mθ7.f 
57/56/0044 32:48 PM 1,908,041,561 ù╤¢▓╕▄C.?Äa
03/08/2052 12:51 AM 2,334,939,216 b
09/20/2103 06:01 AM <DIR> ╔}$╘╖@az.%$
02/08/2071 11:34 AM <DIR> ƒè^å▐Ç.W╠O
06/26/2015 09:46 PM <DIR> Temporary Internet Files
9 File(s)20,997,492,556 bytes
17 Dir(s) 495,407,104 bytes free

>>9
cutest post on /prog/.

CLISP worked pretty well, except it would crash REPL if any key other than `(' was the first one pressed. Weird.

CLISP uses readlines and matches parens, so it's readlines crashing. That's still weird.

>>9
If your filesystem is quite thoroughly trashed, there's nothing that can't happen.

>>1

Dev-C++, a IDE from the early 2000s

DevCpp 5.7.1 was released mid 2014, though.

I have the latest ReactOS version (4.4.0, came out about a month ago) installed in VirtualBox on a Windows 7 host machine. Sometimes when booting up it seems to hang on the loading screen, and with no progess after a few minutes I just reboot it - but when it doesn't get stuck it does boot much faster than Windows 7 (though I can't say if that's due to the OS or if it's a VM versus real hardware issue). The basic "framework" of a Windows operating system is clearly there, but it obviously is pretty buggy.

A few days ago I tried installing the VirtualBox guest extensions for Windows (which the ReactOS site says does work, even though it's not real "Windows"), and the installer ran without issues, but upon rebooting, the color depth was dropped down to 256 bits, which also for some reason causes screen updates in Firefox (but not really elsewhere) to "scroll" down the screen, like when loading an image on dial-up. This isn't just with images though, even with a webpage page that's already fully loaded into memory, scrolling up or down has issues. I did change the color settings to 32-bit (the maximum) which stopped the problem, however even though I had applied the setting and was able to see that the display problems stopped, shortly thereafter the system froze and I had to reboot, and upon rebooting it was back at the 256 bit setting. I once again set the color depth to 32-bits, and did a proper shutdown and reboot. Now it seems to be staying at 32 bits - apparently even if display settings are applied, they aren't written to disk until a proper shutdown is done.

It comes with Firefox (version 45.0.1) preinstalled, which is usable, I can actually access websites and stuff, though the Firefox status bar does say it seems slow, probably because the ReactOS network drivers aren't really good. It's downloading Firefox updates now, apparently at a rate of maybe 5-10 seconds per megabyte, which doesn't seem too bad. I just updated it to Firefox 47.0.2, seemingly without problems, but now it's trying to download another 50 meg update, which may take a while...

I was able to get on progrider and actually wrote my original version of this review from within the VM, but it froze and crashed before I could actually post it. The post box was rendered a bit improperly (which is interesting, the OS is alpha but the browser isn't, so apparently the OS works well enough that the browser's rendering engine worked, but not perfectly?), it was no bigger than the name field by default, but I could expand it by dragging the lower right corner - though the first line of my post wasn't visible unless I clicked preview.

Just tried to install the next Firefox update in the VM, and now it says can't load XPCOM. Now I get another message saying procedure entry point CoGetInterceptor can't be found in ole32.dll.

Okay so it looks like that ruined my Firefox, not that I'm surprised. Accocrding to a quick google search on my host machine, the only option is to uninstall and reinstall firefox, which is obviously problematic since ReactOS doesn't have any other browser installed. Fortunately it does come with a package manager, so now I'm using that to install an older Firefox version.

Looks like my VM is pretty much fucked now, somehow the OS thinks the Firefox directory is read-only, so I can't properly remove the old version or install the new version. Looks like I'll just have to reinstall the OS.

Next time though, I'm thinking I'll try seeing if I can get a compiler toolchain installed somehow, and see how well the Windows API is supported. I think I'll also try to make frequent backups of the VM hard drive so I don't have to reinstall whenever something goes wrong. It's pretty much what I'd expect of a Windows clone - it looks outwardly pretty presentable for something at this stage, but the stuff under the hood is pretty susceptible to failure, basically like official Windows but only moreso. Although at this point, I'd estimate the amount of work put into development as around the Windows 95/98 level if we were mapping it to Windows history, so I'm not surprised there are a lot of holes in application support. The Windows API always did seem needless complicated to me, even in the 3.1 days you needed a manual of a few hundred pages just to document it.

I'm displease that we will be start counting months from zero

These are the days.

The Windows API always did seem needless complicated to me, even in the 3.1 days you needed a manual of a few hundred pages just to document it.

That's because it contains the equivalent of most of POSIX + X + Xt + Xaw and then some other even-higher-level GUI APIs (e.g. Qt/GTK for file, font, and color selection dialogs.) The POSIX 2008 standard already contains over 3.8K pages.

2045 The Year of ReactOS on the neural implant