(Forget) Voxel support (we want models and GL!)
Moderator: GZDoom Developers
-
- Lead GZDoom+Raze Developer
- Posts: 49226
- Joined: Sat Jul 19, 2003 10:19 am
- Location: Germany
-
- Posts: 2271
- Joined: Mon May 24, 2004 8:25 am
- Location: Ålesund, Norway
-
- Lead GZDoom+Raze Developer
- Posts: 49226
- Joined: Sat Jul 19, 2003 10:19 am
- Location: Germany
-
- Posts: 2271
- Joined: Mon May 24, 2004 8:25 am
- Location: Ålesund, Norway
While true, the two different systems can perform the same job when it comes to stuff like office work (you don't need a million megabytes of RAM and thirty times that in HD space to work on a spreadsheet or a text document), and on the same platform, but with a great speed difference. DOS is much smaller and therefore works both better and faster. The only thing that limits MS-DOS (not others IIRC) is the 640k conventional memory limit. And it's not really a limit, because you could just use high memory easy as pie.
-
- Lead GZDoom+Raze Developer
- Posts: 49226
- Joined: Sat Jul 19, 2003 10:19 am
- Location: Germany
-
- Posts: 11351
- Joined: Mon Oct 06, 2003 3:41 pm
- Operating System Version (Optional): Windows 10
- Location: United Kingdom
-
- Posts: 766
- Joined: Tue Sep 16, 2003 3:03 pm
And Pixel stands for Picture Element, so therefore we can call it a Volume Element.
Also going slightly offtopic, DOS has a kind of one-track mind. It doesn't need to keep the spyware that's active in the background, or the bugs running in IE, it just has to care about what's running (not really true, but you get the picture).
Also DOS apps have direct access to hardware, while Windows apps do not (sort of).
Also going slightly offtopic, DOS has a kind of one-track mind. It doesn't need to keep the spyware that's active in the background, or the bugs running in IE, it just has to care about what's running (not really true, but you get the picture).
Also DOS apps have direct access to hardware, while Windows apps do not (sort of).
-
- Posts: 2271
- Joined: Mon May 24, 2004 8:25 am
- Location: Ålesund, Norway
Yeah, only one thing can run at the same time. That'd mean that you'd install any virus your computer would get yourself instead of Windows doing it for you. Any spyware would have to be loaded as a TSR (and would thus be very hard to cloak (just do a "mem /c | more"), plus it'd have to be listed in autoexec.bat or config.sys for automatic startup), so I'd say DOS is at least one thousand times more secure than Windows, even though all the applications have direct hardware access (which isn't a bad thing, at least IMHO)...
-
- Posts: 2697
- Joined: Thu Aug 26, 2004 1:23 pm
-
- Lead GZDoom+Raze Developer
- Posts: 49226
- Joined: Sat Jul 19, 2003 10:19 am
- Location: Germany
jallamann wrote: Any spyware would have to be loaded as a TSR (and would thus be very hard to cloak (just do a "mem /c | more"), plus it'd have to be listed in autoexec.bat or config.sys for automatic startup), so I'd say DOS is at least one thousand times more secure than Windows,
Don't be too sure about that. DOS viruses had their way of cloaking themselves, preferably by hiding themselves in other programs' memory.
-
- Posts: 2271
- Joined: Mon May 24, 2004 8:25 am
- Location: Ålesund, Norway
But as I said, you'd have to actually install the virus yourself, be it through a batch file or another program that claims it's something else, but it would be far harder for virus authors to infect computers than today's Windows vulnerabilities. And by hiding in other programs' memory, they could be pinpointable. AFAIK, most TSR's have a fixed memory consumption, so if a value is off by just a kilobyte, you could know where the problem would be. And if you have an antivirus application, it probably wouldn't be hard to get rid of virii, should you be unfortunate enough to ever get any.
-
- Lead GZDoom+Raze Developer
- Posts: 49226
- Joined: Sat Jul 19, 2003 10:19 am
- Location: Germany
You have no idea. I once got a DOS virus through some infected software (that was 1990.) How should I have noticed that? Unlike Windows viruses in DOS they were not separate programs that had to be installed. They spread by attaching themselves to other programs. As a result they spread like a plague.
And regarding removal, it isn't that simple. The one I got was resistant to everything that dealt with such infections at the time. The only means I was able to get rid of it was to use Norton Disk Editor and manipulate the boot sector in a very specific way so that running a HD checker later could detect the corrupted sector. That thing was as nasty and persistent as most modern Windows viruses, believe me.
Of course after finding that thing I took it apart with a disassembler. It was a truly nasty piece of work.
And regarding removal, it isn't that simple. The one I got was resistant to everything that dealt with such infections at the time. The only means I was able to get rid of it was to use Norton Disk Editor and manipulate the boot sector in a very specific way so that running a HD checker later could detect the corrupted sector. That thing was as nasty and persistent as most modern Windows viruses, believe me.
Of course after finding that thing I took it apart with a disassembler. It was a truly nasty piece of work.
-
- Posts: 2271
- Joined: Mon May 24, 2004 8:25 am
- Location: Ålesund, Norway
-
- Posts: 4631
- Joined: Fri Apr 16, 2004 1:41 pm
- Preferred Pronouns: He/Him
Enough of this derailness.
I tought that colision support for voxels was coded in.. (think: Blood in Zdoom) but not their rendering..?

I tought that colision support for voxels was coded in.. (think: Blood in Zdoom) but not their rendering..?
Rather no.. seing as each of his "fake voxels" is an independant thing it lags as hell.. at least for meKirby wrote:Couldn't we just stick with Phoenix's FVoxels? I'd think those are at least satisfactory
