WinXP Pro, Version 2002, Service Pack 3nitro2k01 wrote:Which service pack?
CCleaner says: "Windows XP Service Pack 3", Install Date "2011-03-04", Version "20080414.031514"
Moderator: Moderators
That's on a P4 1.7GHz ... how can this run fullspeed on a 200MHz system? Perhaps he is doing something wrong?creaothceann wrote:For comparison, time to complete the CT intro:
- 00:38 (492.11%) ZSNES 1.51
- 01:18 (239.74%) SNES9x 1.53
- 01:42 (183.00%) no$sns 1.0
- 03:07 (100.00%) realtime
(FD: mine runs at 30% speed :P)
That is a rather insulting insinuation :Pnitro2k01 wrote:So have I. Now it will be interesting to see if byuu will approve my post.
Thanks! Should be fixed now (unless I got something else wrong).The e-mail address in the spam-shielded box is incorrect. The second r is missing.
Thanks for the info. Nasty... The thing that I liked about the .hlp stuff has been that it showed only one chapter at a time.The help files that are created by no$*** are incompatible with modern versions of Windows (XP with later service packs and later.)
Haven't really checked myself... I tried to run it on my old 200MHz computer last week, but it reported HDD not found, and after a few minutes it blew the fuse of the power supply... so, actually, I am able to confirm that it DOESN'T WORK on my 200MHz computer.how can this run fullspeed on a 200MHz system?
Backgound: I registered a year ago and was almost sure I posted something back then. Approving the first post makes sense, but if you need manual approval for more than one post, you're likely trying very concerned about what people are saying. In other words, what I said was based on an incorrect assumption.byuu wrote:That is a rather insulting insinuationnitro2k01 wrote:So have I. Now it will be interesting to see if byuu will approve my post.
True for all emulators, and their todo-lists are tendencially growing, making it quite impossible to get finished.Perfecting an SNES emulator, however, takes many years.
The problem is that the NES is hardly a simple 6502 based system... in fact emulating the 6502, even if you write your own core is a breeze. The PPU has a lot of tricks also, and probably one has to spend quite some time figuring it out fully... then you discover than your emulator can only execute a handful of games from the first era of the NES... then you start with the MMCs... and your life as you knew it is over :pnocash wrote:For an old "6502-based" system, it was more complicated than expected. I started in 2006, but gave up after a few months. And then resurrected the project in late 2010, alltogether, I worked around 20 months on it (lots of the time being blown up on the obscure add-ons though).True for all emulators, and their todo-lists are tendencially growing, making it quite impossible to get finished.Perfecting an SNES emulator, however, takes many years.
nocash was speaking of the SNES, which is 6502-derived.The problem is that the NES is hardly a simple 6502 based system... in fact emulating the 6502, even if you write your own core is a breeze. The PPU has a lot of tricks also, and probably one has to spend quite some time figuring it out fully... then you discover than your emulator can only execute a handful of games from the first era of the NES... then you start with the MMCs... and your life as you knew it is over :p
I misread him... however by comparison, if a NES emulator gets though when implementing mappers that pale in comparison to the most common of the chips the SNES uses in-cartrige... it's obvious that trying to write an emulator (not to mention if you want a precise one) is several orders of magnitude more complex than a NES one.byuu wrote:nocash was speaking of the SNES, which is 6502-derived.The problem is that the NES is hardly a simple 6502 based system... in fact emulating the 6502, even if you write your own core is a breeze. The PPU has a lot of tricks also, and probably one has to spend quite some time figuring it out fully... then you discover than your emulator can only execute a handful of games from the first era of the NES... then you start with the MMCs... and your life as you knew it is over :p
Again though, as I've said, the NES is a walk in the park in comparison. I've done both, I should know. The NES PPU has eight registers, and full documentation on what every single cycle does. The SNES PPU has 64 registers that are all bit-packed with multiple functions, and defies attempts to be documented even at the scanline level.
Not saying you shouldn't be proud of an NES emulator. A PS1 emulator is way harder than SNES, PS2 way harder than PS1, and PS3 way harder than PS2. With progress comes added complexity.