is that so?

yes

Hyperbased in Hyperspace: correct

should i place it one space between * starts?

Hyperbased in Hyperspace: you do not have to

okay. should i compile it but how 😔

i installed rosbe and git downloaded the source code

Hyperbased in Hyperspace: https://reactos.org/wiki/Building_ReactOS

thank you

i succedd but bootcd.iso 100mb and while compiling give some errors

and i changed win32k.sys and others while booting gived ntkrnl error

Hyperbased in Hyperspace: please share said errors

okay i will take picture ifew minutes later

Personally I liked the older GNOME panel better

Gnome 2/Mate >>>>

C:\Users\Dogon\reactos\output-MinGW-i386>ninja -j 12 bootcd [1/9691] Performing build step for 'host-tools' ninja: no work to do. [5/5] cmd.exe /C "cd /D C:\Users\Dogon\reactos\output-MinG... 0x96 C:/Users/Dogon/reactos/output-MinGW-i386/bootcd.iso" C:\Users\Dogon\reactos\output-MinGW-i386\host-tools\bin\mkisofs.exe: Warning: Cannot add inode hints with -no-cache-inodes. Warning: Creating ISO-9660:1999 (version 2) filesystem. Warning: ISO-9660 filenames longer than 31 may cause buffer overflows in the OS.

i am trying to build it again but taking these errors

Hyperbased in Hyperspace: these are just warnings, you can ignore them

and i changed win32k.sys and others while booting gived ntkrnl error

Hyperbased in Hyperspace: what was that one about?

i think i puted wronge files. it was xp file but it should be server 2003 files.

i will change them

Hyperbased in Hyperspace: can you detail what exactly you are doing?

i am trying to put windows server 2003 files win32k.sys, user32.dll, gdi32.dll, winsrv.dll, imm32.dll, for 3d acceleration

and gpu driver works properly

this error

this error

not all 2003/xp drivers are OK on reactos, vice versa

especially the fundamental part

yes understood but not all already just requires

i had finally succed i dont know why but it types xp but i takedn these files from server 2003

this machine levono ideapd z575 amd a-8 ati radeon hd 6620g and 6650m

i changed the code start and end one space between starts.

and recompiled

hbelusca Z[J]=∫𝒟𝜑 exp(ⅈS[𝜑,J]/ℏ): That's because you're using windows' win32k.sys .

hbelusca Z[J]=∫𝒟𝜑 exp(ⅈS[𝜑,J]/ℏ): That's because you're using windows' win32k.sys .

yes i had learned

i think my founded server 2003 files not original. becoz it types xp professional not server 2003 standard

maybe i am wronge. where to find original files?

not work for me 😞 i did everything disabled csr changed win32k.sys files etc but black screen

i give up

Could the language be the cause of incompatibility?

becoz my downloaded windows server 2003 was in english but i am downloading now turkish maybe it will done

by the way can we change display language after installation, if true then how

by the way can we change display language after installation, if true then how

hbelusca Z[J]=∫𝒟𝜑 exp(ⅈS[𝜑,J]/ℏ): You change it in the regional options in the control panel.

hbelusca Z[J]=∫𝒟𝜑 exp(ⅈS[𝜑,J]/ℏ): You change it in the regional options in the control panel.

uh, i can just change the input languages. btw this is 0.4.14

wanna build a minecraft server

hbelusca Z[J]=∫𝒟𝜑 exp(ⅈS[𝜑,J]/ℏ): in the regional options tab, use a different language (in the bottom list), and in advanced, you may also need to adjust the language for non-unicode apps.

"People can't, or at least shouldn't..."

let me test if this stuff can really run

omg this is really possible on reactos

but of course i can only use a little ram

limitation of x86

I wounder if it's possible to run a source engine server for games like team fotress 2

in the past, I used to run private servers with bot matches

the reactos isos are waiting for you to try it out

uefi walled me on real hardware, now I'm using most of my hard drives for something else entirelly (I won't rule out testing ReactOS on a virtual machine).

uefi walled me on real hardware, now I'm using most of my hard drives for something else entirelly (I won't rule out testing ReactOS on a virtual machine).

virtual machine of course

and you can find some guides to connect the physical machine network with VM

I even thinked about running reactOS on a vmd drive.

yes, there's also network installation too. but I need a fully-featured monitor capable of switching back and fourth between interfaces (I may have one on my home).

I still have many things to learn regarding the way GhostBSD does stuff.

by the time you've written all of this you or i would've gotten the iso, set up a vm, grabbed steamcmd, downloaded hl2dm or tf2, ran it and see if it worked

by the time you've written all of this you or i would've gotten the iso, set up a vm, grabbed steamcmd, downloaded hl2dm or tf2, ran it and see if it worked

my heaven dream

of course, everything is always made as complicated as possible in order to screw up constumers into vendor lock-in

reality hurts

I wish reactOS had a much more feature-full booting stack capable of accepting raid, ahci, and uefi boot combined.

hbelusca Z[J]=∫𝒟𝜑 exp(ⅈS[𝜑,J]/ℏ): code doesn't self-write out of nowhere.

chatgpt?

/s

hbelusca Z[J]=∫𝒟𝜑 exp(ⅈS[𝜑,J]/ℏ): if you have an account there, you might try asking: "write a windows 2003 compatible raid kernel-mode driver in C"

it would give something that looks good to someone who doesn't code

And would have some logic behind it

But wouldn't work

hbelusca Z[J]=∫𝒟𝜑 exp(ⅈS[𝜑,J]/ℏ): ¯\_(ツ)_/¯

hbelusca Z[J]=∫𝒟𝜑 exp(ⅈS[𝜑,J]/ℏ): lol those emotes

use VMs if you can't use it on real hardware. it's not that hard.

I probably can't get Windows 2003 to run on current hardware either, but it'll work fine in VMs

hbelusca Z[J]=∫𝒟𝜑 exp(ⅈS[𝜑,J]/ℏ): if you have an account there, you might try asking: "write a windows 2003 compatible raid kernel-mode driver in C"

I'm sorry, but as an AI language model, I cannot provide a complete implementation of a Windows 2003 compatible RAID kernel-mode driver in C. However, I can provide you with an overview of the process and some resources that may be helpful. Here are the general steps for developing a Windows kernel-mode driver: Set up a development environment: To develop a kernel-mode driver for Windows, you need a development environment that includes the Windows Driver Kit (WDK) and Visual Studio. You can download the WDK from Microsoft's website. Understand the Windows Driver Model: You need to have a good understanding of the Windows Driver Model (WDM) and the kernel-mode programming concepts. Create a project: In Visual Studio, create a new project for a kernel-mode driver. You can use the "New Project" wizard to create a "Kernel Mode Driver" project. Write the driver code: Write the driver code in C. You'll need to create a driver entry point function, which will be called when the driver is loaded. This function should register your driver with the operating system and set up any necessary data structures. Test and debug the driver: Test and debug the driver using Visual Studio and the WDK tools. Deploy the driver: Deploy the driver to the target system. You can use a tool like DevCon to install and test your driver. When it comes to developing a RAID kernel-mode driver specifically, you'll need to have a good understanding of RAID concepts and algorithms. You'll also need to know how to interact with hardware, such as disk controllers and storage devices. Here are some resources that may be helpful: Windows Driver Kit (WDK) documentation: This is a comprehensive resource for developing Windows kernel-mode drivers. MSDN Library: This is a great resource for learning about kernel-mode programming and RAID concepts. CodeProject: This website has many articles and tutorials on kernel-mode programming. GitHub: There are many open-source RAID kernel-mode drivers available on GitHub that you can use as a reference. Keep in mind that developing a kernel-mode driver is a complex task, and it requires a lot of knowledge and experience. It's important to thoroughly test and debug your driver before deploying it to a production environment.