quakespasm VS ftequake

Quakespasm https://github.com/sezero/quakespasm

Forget the GOG version and grab a modern source port like Quakespasm: https://sourceforge.net/projects/quakespasm/

I wouldn't say you absolutely need to get a new PC. You could probably try using the QuakeSpasm engine. Pretty much any modern PC can run Quake, the "remaster" just has much higher system requirements than usual.

Can you elaborate on what you understand the correct location to be? Does this mean you have placed your music folder inside of your id1 directory? Are your music files named correctly, e.g. track02.[ogg,mp3,wav, or flac]~track11.[ogg,mp3,wav, or flac]? Have you looked at the documentation on music support in Quakespasm?

Get Quakespasm and drop the files in your Steam/steamapps/common/quake/rerelease folder, and use that executable to play the game. It'll work on older computers.

Yesterday a new update to Quakespasm came out. You can get it here.

Grab at sourceforge.

( I have sucessfully integrated a .net rewrite (https://github.com/Memorix101/SharpQuake) of the quake engine into unity and I've seen someone else do it for UE4. I'm working on PLUQ, which is a nanomsg nng interface integrated into an modern Quake engine (https://github.com/sezero/quakespasm, https://github.com/mdeguzis/ftequake, ...) that on game/level load provides geometry, textures, entities, ... and at runtime a bidirectional channel for the data (enity positions and inputs) needed to render and steer the game from a connected client. The connected client can e.g. be the rendering and input part of the original engine or something Unity3D, Unreal, Godot, ... based. I hope to open up Quake for experimentation using non GPL engines with this...)

I used QuakeSpasm.

( I have sucessfully integrated a .net rewrite (https://github.com/Memorix101/SharpQuake) of the quake engine into unity and I've seen someone else do it for UE4. I'm working on PLUQ, which is a nanomsg nng interface integrated into an modern Quake engine (https://github.com/sezero/quakespasm, https://github.com/mdeguzis/ftequake, ...) that on game/level load provides geometry, textures, entities, ... and at runtime a bidirectional channel for the data (enity positions and inputs) needed to render and steer the game from a connected client. The connected client can e.g. be the rendering and input part of the original engine or something Unity3D, Unreal, Godot, ... based. I hope to open up Quake for experimentation using non GPL engines with this...)