Anyways, with that being said, I've tried to run 0.4.13 on three separate machines with the following specs: Not sure if you're not doing that already, but I would suggest trying to boot the ReactOS installer from RAM disk , since this is the most reliable way to boot ReactOS. MSI B350M mobo Gigaby...

Colin Finck wrote: ↑

Wed Apr 01, 2020 10:19 am

I've increased the per-file attachment size to 512 KB. Hope that's sufficient for a while
Thanks for trying it out and editing your previous posts!

Now all my screenshots are attached, the real hw photos I just downscaled and I think they still look decent

To fix that permanently, I have enabled attachments on the forum. You can now attach your awesome screenshots to your forum posts and be confident that they still exist tomorrow. Very nice! Although I can't attach some screenshots and real hw photos, could it be possible to increase the attachement...

jimtabor wrote: ↑

Fri Mar 27, 2020 8:50 pm

Is your Router/Switch 1GBits?

I was using the network share from another desktop (which is connected to the router through WLAN), and yes it was Gigabit network.

ReactOS booted from xHCI USB drive on AMD X570 system, using the modded AMD xHCI XP driver from win-raid , disk_new, usbstor.sys v. 5.3.1201.0 from POSReady 2009 ISO and with PR#1569 applied. KYOeLvb.png Only one of three xHCI controllers on the system appears to be usable, although I believe this i...

Mame64 on ReactOS x64, running IRIX 6.2 on Indigo2 emulated system: The latest version of Mame64 (0.218) is x64 only and NT 6+, so additional NT 6+ exports were needed.

Here's some stuff I tried on ReactOS x64 build: CPU-Z 1.91 x64: VirtualBox_ReactOS_18_01_2020_04_00_51.png Running on real hardware (Z170 Pro4S) as well: IMG_20200122_1857392.jpg 7-zip 19.00 x64: VirtualBox_ReactOS_17_01_2020_19_28_47.png Waterfox 30: VirtualBox_ReactOS_18_01_2020_03_28_37.png

mrmajik45 wrote: ↑

Wed Oct 23, 2019 3:38 pm

I have it set to 4gb of ram

Try to allocate no more than 3585 MB of system memory when you use Guest Additions, otherwise ReactOS would crash on VBoxDisp.dll, like on your screenshots.

I'm really curious how you did it. I've tried with NT4 and ext2ifs driver and got "Unknown hard error" (on blue boot screen) after booting it from ext2 partition with FreeLDR. No idea where I made mistake. You need to load all the needed drivers at boot-time (change the Start value to 0 for each ke...

ReactOS booted from RAM disk with write access to the boot volume (using the Windows 2003 RAM disk driver), the volume on HDD image is formatted using ext2 file system.

ReactOS boots from the ext2 volume, thanks to the recent ext2 fixes in FreeLDR Because of FreeLDR still lacking a working ext2 boot sector, I have installed FreeLDR on another FAT32 volume.

EDIT:
FreeLoader is able to boot Windows from ext2 volume as well.

I burn the release image and there is a folder where installfreeldr is located. You don't need to do that. You just extract the installfreeldr and setupldr.sys, then run installfreeldr and write bootsector on your USB drive, which you already did. Now what you need to do is to copy setupldr.sys fro...

Any ideas ? Lenovo Y520 15IKBN is an Intel 170 chipset based laptop. Since it has no optical drive and has only the xHCI USB ports, the two only ways to boot ReactOS are RAM boot or PXE boot . Please refer to one of these tutorials, if you get past that and it still fails (you might have issues eg....

Windows 8 x64 in VirtualBox 2.1.0 running on ReactOS, x64 guest virtualization needs VT-x capable hardware (in this case, a Lenovo Y50). ReactOS x64 works as well

Seems i was mistaken hardware OpenGL fails with ATI drivers i didn't realize you have to manually select the driver AFAIK you shouldn't actually override the graphics renderer with ones provided by GPU driver, it tends to cause issues and these should be already set as "System Default". To determin...