Ako ste ikad pokušali dobiti vintage računalnu igru gore i trčanje na modernom sustavu, vjerojatno ste bili šokirani kakobrzo igra je vodila. Zašto stare igre ostanu bez kontrole nad modernim hardverom?
Ranije smo vam pokazali kako upravljati starijim softverom na suvremenim računalima; današnja pitanja o pitanjima i odgovorima predstavlja lijepi kompliment koji ukazuje na to zašto neki stariji softver (posebice igre) nikad ne čini ispravnim kada ih pokušate pokrenuti na suvremenom hardveru.
Današnja pitanja i odgovori nam se javljaju zahvaljujući SuperUseru - podjele Stack Exchange-a, zajednice-driven grupiranja Q & A web stranica.
Pitanje
SuperUser čitač TreyK želi znati zašto stare računalne igre luduju brzo na novom hardveru:
I’ve got a few old programs I pulled off an early 90s-era Windows computer and tried to run them on a relatively modern computer. Interestingly enough, they ran at a blazing fast speed – no, not the 60 frames per second kind of fast, rather the oh-my-god-the-character-is-walking-at-the-speed-of-sound kind of fast. I would press an arrow key and the character’s sprite would zip across the screen much faster than normal. Time progression in the game was happening much faster than it should. There are even programs made to slow down your CPU so that these games are actually playable.
I’ve heard that this is related to the game depending on CPU cycles, or something like that. My questions are:
- Why do older games do this, and how did they get away with it?
- How do newer games not do this and run independently of the CPU frequency?
Pa što je to priča? Zašto točno špijuni u starim igrama plamenju preko zaslona tako brzo igra postaje nemoguće igrati?
Odgovor
JourneymanGeek šalje ga SuperUser suradnikom:
I believe they assumed the system clock would run at a specific rate, and tied in their internal timers to that clock rate. Most of these games probably ran on DOS, and were real mode (with complete, direct hardware access) and assumed you were running a iirc 4.77 MHz system for PCs and whatever standard processor that model ran for other systems like the Amiga.
They also took clever shortcuts based on those assumptions including saving a tiny bit of resources by not writing internal timing loops inside the program. They also took up as much processor power as they could – which was a decent idea in the days of slow, often passively cooled chips!
Initially one way to get around differing processor speed was the good old Turbo button (which slowed your system down). Modern applications are in protected mode and the OS tends to manage resources – they wouldn’t allow a DOS application (which is running in NTVDM on a 32-bit system anyway) to use up all of the processor in many cases. In short, OSes have gotten smarter, as have APIs.
Heavily based off this guide on Oldskool PC where logic and memory failed me – it’s a great read, and probably goes more in depth into the “why”.
Stuff like CPUkiller use up as many resources as possible to “slow” down your system, which is inefficient. You’d be better off using DOSBox to manage the clock speed your application sees.
Ako ste znatiželjni o tome kako je stvarni kôd implementiran u ranijim računalnim igrama (i zašto se tako slabo prilagođavaju modernim sustavima, a da se ne miješaju u neku vrstu emulacijskog programa), predlažemo i provjeru ove dugotrajne, ali zanimljive kvarove proces u drugom SuperUser odgovoru.
Imate li nešto za objašnjenje? Zvuči u komentarima. Želite li pročitati više odgovora od drugih tehnoloških korisnika Stack Exchangea? Pogledajte ovdje cijelu raspravu.
