Register - Login
Views: 99383505
 Main - Memberlist - Active users - Calendar - Wiki - IRC Chat - Online users
Ranks - Rules/FAQ - Stats - Latest Posts - Color Chart - Smilies		 04-24-22 02:11:53 AM
Jul - The Cutting Room Floor - Star Fox Adventures E3 2002 prototype (5/17/02) New poll - New thread - New reply
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 ... 33 34 35 36 37 38 39 40 41 42 Next newer thread | Next older thread
nmgschris
User
Level: 8


Posts: 1/10
EXP: 1757
For next: 430

Since: 11-09-13

From: Hanoi, Vietnam

Since last post: 8.4 years
Last activity: 8.1 years
Posted on 11-11-13 02:03:57 PM (last edited by nmgschris at 11-12-13 03:15:16 AM) Link | Quote
Tracking the thread since last Saturday, things are getting interesting, especially the restoration of the ROM.

Anyway, have anyone know what is in ROM:000FA0B0 in DLLS.bin ?
zoinkity

Level: 13


Posts: 13/27
EXP: 8319
For next: 1948

Since: 09-07-12


Since last post: 4.6 years
Last activity: 4.5 years
Posted on 11-11-13 04:30:53 PM Link | Quote
I might as well be the one who gives the bad news ;*)

Please let me do the honor of dashing your hopes and dreams about DLLS.bin containing anything resembling the original game code.
What it is is still very interesting. This is an inbetweener file generated by the compiler, similar in purpose to an object or library file. Basically, it's unlinked N64 code. Supposing you had an SDK you could probably force their particle effects engine into service ;*) (presuming you rewrote the tabs and all)

This does answer the tiny question of why the stack is always moved one word further than it really needs to be, and why GP is never used in normal code. All functions in DLLS are preceded by a blank LA GP. GP would be set externally to the base address of the function block (which is not necessarily the function itself), and as you can see this base address is used for expanding the commands into final addresses. JALRs are computed and replaced with JALs in most cases, and the simplified functions are written to the final ROM.

DLLS only contains a few, albeit interesting, functions for generating display lists and managing object structs. It doesn't have what you would call 'engine code'. In fact, it doesn't even include the rarezip decompressor, and certainly doesnt' include anything from the standard library. How these compare to previous iterations of the same effect generators would be an interesting study, but you aren't looking at an N64 version of the game. Oh no, that would be laughable. HOHOHOHO!

This whole affair reveals what Rare hackers have been saying for years: they really need to clean their build directories from time to time.
Hugo_Peters

Level: 26


Posts: 39/147
EXP: 99206
For next: 3069

Since: 10-29-13

From: The Netherlands

Since last post: 1.9 years
Last activity: 1.1 years
Posted on 11-11-13 04:44:58 PM Link | Quote
Originally posted by zoinkity
I might as well be the one who gives the bad news ;*)

Please let me do the honor of dashing your hopes and dreams about DLLS.bin containing anything resembling the original game code.
What it is is still very interesting. This is an inbetweener file generated by the compiler, similar in purpose to an object or library file. Basically, it's unlinked N64 code. Supposing you had an SDK you could probably force their particle effects engine into service ;*) (presuming you rewrote the tabs and all)

This does answer the tiny question of why the stack is always moved one word further than it really needs to be, and why GP is never used in normal code. All functions in DLLS are preceded by a blank LA GP. GP would be set externally to the base address of the function block (which is not necessarily the function itself), and as you can see this base address is used for expanding the commands into final addresses. JALRs are computed and replaced with JALs in most cases, and the simplified functions are written to the final ROM.

DLLS only contains a few, albeit interesting, functions for generating display lists and managing object structs. It doesn't have what you would call 'engine code'. In fact, it doesn't even include the rarezip decompressor, and certainly doesnt' include anything from the standard library. How these compare to previous iterations of the same effect generators would be an interesting study, but you aren't looking at an N64 version of the game. Oh no, that would be laughable. HOHOHOHO!

This whole affair reveals what Rare hackers have been saying for years: they really need to clean their build directories from time to time.

You seem to know a lot of it. I already knew from Phil that we are missing the main N64 executable, but DLLS.bin does more than just "generating display lists and managing object structs". I don't have permission from Phil yet, but I'm going to post this here anyways (all rights to Phil Tossell and what not):

"While DLLS.bin contains much of the (mainly gameplay) code (we had a DLL system so we could swap code in and out to save space on N64), what you don't have is the main N64 executable which contains most of the systems code". So there is indeed a part missing, but it's not correct to say we're missing almost everything, in fact, it seems to me only a small bit is missing (look at the size of DLLS.bin, and the amount of strings found inside it. Also functions for the audio can be found.)

____________________
I have a blog: clyck!
CoinCollector
Random nobody
Level: 8


Posts: 8/8
EXP: 1658
For next: 529

Since: 08-05-07


Since last post: 8.4 years
Last activity: 1.7 years
Posted on 11-11-13 06:18:32 PM Link | Quote
Bummer, but thanks you guys - really nice to know one way or the other!

Man. N64 games are so small compared to Gamecube. Wish they would've just, you know, slipped the entire compiled thing in, hidden away on the disc somewhere. Just one quick drag & drop... ah well. I'm confident we *will* play it someday!

And great work everybody, getting those models, sounds, etc out! Really really cool to have those.
Hugo_Peters

Level: 26


Posts: 40/147
EXP: 99206
For next: 3069

Since: 10-29-13

From: The Netherlands

Since last post: 1.9 years
Last activity: 1.1 years
Posted on 11-11-13 06:21:53 PM Link | Quote
Originally posted by CoinCollector
Bummer, but thanks you guys - really nice to know one way or the other!

Man. N64 games are so small compared to Gamecube. Wish they would've just, you know, slipped the entire compiled thing in, hidden away on the disc somewhere. Just one quick drag & drop... ah well. I'm confident we *will* play it someday!

And great work everybody, getting those models, sounds, etc out! Really really cool to have those.

Heh, we're, or I anyways, are not done with this at all.

____________________
I have a blog: clyck!
nmgschris
User
Level: 8


Posts: 2/10
EXP: 1757
For next: 430

Since: 11-09-13

From: Hanoi, Vietnam

Since last post: 8.4 years
Last activity: 8.1 years
Posted on 11-11-13 11:34:46 PM (last edited by nmgschris at 11-12-13 04:09:19 AM) Link | Quote
Originally posted by Hugo_Peters
Originally posted by zoinkity
I might as well be the one who gives the bad news ;*)

Please let me do the honor of dashing your hopes and dreams about DLLS.bin containing anything resembling the original game code.
What it is is still very interesting. This is an inbetweener file generated by the compiler, similar in purpose to an object or library file. Basically, it's unlinked N64 code. Supposing you had an SDK you could probably force their particle effects engine into service ;*) (presuming you rewrote the tabs and all)

This does answer the tiny question of why the stack is always moved one word further than it really needs to be, and why GP is never used in normal code. All functions in DLLS are preceded by a blank LA GP. GP would be set externally to the base address of the function block (which is not necessarily the function itself), and as you can see this base address is used for expanding the commands into final addresses. JALRs are computed and replaced with JALs in most cases, and the simplified functions are written to the final ROM.

DLLS only contains a few, albeit interesting, functions for generating display lists and managing object structs. It doesn't have what you would call 'engine code'. In fact, it doesn't even include the rarezip decompressor, and certainly doesnt' include anything from the standard library. How these compare to previous iterations of the same effect generators would be an interesting study, but you aren't looking at an N64 version of the game. Oh no, that would be laughable. HOHOHOHO!

This whole affair reveals what Rare hackers have been saying for years: they really need to clean their build directories from time to time.

You seem to know a lot of it. I already knew from Phil that we are missing the main N64 executable, but DLLS.bin does more than just "generating display lists and managing object structs". I don't have permission from Phil yet, but I'm going to post this here anyways (all rights to Phil Tossell and what not):

"While DLLS.bin contains much of the (mainly gameplay) code (we had a DLL system so we could swap code in and out to save space on N64), what you don't have is the main N64 executable which contains most of the systems code". So there is indeed a part missing, but it's not correct to say we're missing almost everything, in fact, it seems to me only a small bit is missing (look at the size of DLLS.bin, and the amount of strings found inside it. Also functions for the audio can be found.)

You know, maybe the main executable is still somewhere in the disc, if not we could try to swap stuffs in DKR with what we found IF it's the same game format with DP like Hugo said earlier IF compatible.

And, another solution, but i think it's nearly impossible, port entire contents to GC, including gameplay code, then swap with SFA, since the game was port for GC, all contents might from the build they used to port. Same engine, just a little more improvement as the same glitch as DP.

Still a lot of stuffs to do, not giving up hope yet.
KCat
Member
Level: 15


Posts: 2/42
EXP: 15122
For next: 1262

Since: 11-10-13


Since last post: 4.4 years
Last activity: 3.6 years
Posted on 11-13-13 10:42:56 AM (last edited by KCat at 11-13-13 01:49:59 PM) Link | Quote
Originally posted by koolaidman
Rare games sometimes used the AMSeq format for their N64 games. I told SubDrag that there was data in AUDIO.bin that looked like the sequence format in Diddy Kong Racing and he was able to add support in N64MidTool for it. There are some problems with the converted sequences as I said when I released everything, here are some that I encountered:

1.) Pitch problems - as you said, there are some pitch problems in songs that heavily depend on it. For the song you listed I tried to shrink the pitch change values but nothing seemed to sound quite right so I left it to go work on other songs. For that song in particular I knew it was exactly the same as the one used in SFA so I figured it wasn't important to fix that particular one, but you're right that there are more that aren't used that have the same problem. But sometimes there were songs (like Discovery Falls) where the pitch changes are actually too weak. And most of the other songs had pitch changes that were just right. So you'll have to talk to SubDrag about this one.

2.) Program/Patch changes mid song - this wasn't much of a problem since ValleyBell's program worked wonderfully to split the individual channels that had changes and carry their pitch/patch settings over. But since it was an automated process it might've messed some stuff up (in fact there were one or two songs that didn't want to go through his program so I had to resave the MIDI file from a DAW elsewhere and open that up instead). One song that really had this problem bad was the Northern Wastes one. This song is really crazy as it basically has 3 songs in one MIDI file (a lot of the songs do this), each song with it's own channels and using some channels from the other songs. Thankfully I was able piece together something based on IOnEI Falcon's 1 hour video and the officially released version (during the game's original production) but it still sounds inaccurate because I wasn't as familiar with the song at the time so I just left it as is. There were a lot more problems with this song specifically which I'll get into later.

3.) Possible missing channels/notes - not as much as a problem because there weren't many places where it seemed like it was missing channels/notes. The only places that seemed noticeable were the ones for the Test of ____ tracks and Ice Mountain Race where the vocals were missing but the voice samples are actually still in MUSIC.bin (where all the other instrument samples are kept). The officially released music from DP was probably not taken directly from an N64, so there were probably some things that needed to be fixed during the conversion process to the game.

4.) Incorrect notes - also not as much of a problem, but there were some songs that seemed to be using the wrong samples (originally, Discovery Falls was like this but was an easy fix). This might have more to do with the soundfont I made rather than the converted MIDI, but I remember double checking this to make sure it wasn't a problem in other songs but I still ended up having the same problem here and there. (00000052 00081BD8 being the biggest case since nothing seems to work for it and there's no telling what the original sounded like).

5.) Problems with the soundfont - As I said, the instrument samples were taken from MUSIC.bin. The samples were extracted with N64SoundTool, which also has it's share of problems too. Luckily, the majority of the samples in MUSIC.bin were exactly 22khz, but there were still some that had a different rate. I had to manually fix this in Audacity, but since the samples had to be rerendered I lost the root key and loop point for the sample so these had to be recalculated. As a result, there are some parts where the instruments sound a little off, the biggest offender being the piano patch (which I still have no clue how to fix since it appears to be right but still sounds way off). To make matters worse, a lot of the patches used a variety of samples (for instance, there was one patch that had vocal expressions, drums, AND sfx all in one) and to top it all off, instead of having each sample have one root key the game spans the sample across multiple keys in range of the root key. Luckily I don't think I messed that up, but there might be problems with some of the samples themselves still.

6.) No looping - can't be helped I think. You can use some creative license to make up your own loop point for the song though. A lot of the songs sound very good even without a loop, like a soundtrack version.

I've done quite a bit of hacking around with the sound and midi files in recent days, and I think I've come to a good, if broad, understanding of them. Enough so that I could make my own extractors and stupid'n'simple converters, at any rate. Here's some things I've noted:

Pitch problems -- what sticks out to me here is that the instrument sounds contain parameters for detune and bend range, along with attack/release/decay times and key base/ranges and other things. Were these preserved in creating the soundfont? I've yet to look into the sf2 format very much, or the soundfont you provided, but missing the detune and bend range info could probably account for some of the off-key issues.

Program/Patch changes mid song -- I'm not sure where this is actually an issue, at least in the technical sense. I've been able to track-for-track convert the songs and they will play fine. Though as noted, there are some peculiarities in that some songs are actually multiple songs in one (e.g. the Northern Wastes), but I imagine these would be handled by fading in and out specific tracks during gameplay... probably by having an extra 'master' volume control per track that can be controlled externally by the game logic. So to 'extract' the individual songs, you'd just mute specific tracks.

Possible missing channels/notes -- This still has me stumped. There's a couple possibilities I can think of. One, the data just isn't there for some reason. For the ice mountain race, perhaps the devs thought the vocals didn't fit with the visuals or gameplay and took them out for the in-game version. The other possibility is that they're there, but are somehow triggered by game logic. For the Krazoa tests, I could imagine the game logic signaling the audio system with a specific "Test of ___" 'instrument' to use based on which test the player was doing (which would be an odd way to do it surely, especially since the tests seem to have their own songs, but I've seen games do some really odd things before).

Another side issue here is with MIDI itself. In General MIDI, track channel 10 (don't know why I said track) is designated as the percussion/drum channel, and defaults to using bank 128 where the standard drum set is. Music creation programs tend to let you easily change that, so it may not be an issue for generating flacs or mp3s, but people that play the MIDIs using the soundfont will have wrong or missing output for that channel (and unfortunately you may not be able to move it if a given song needs all 16 channels).

Incorrect notes -- Notes that have the wrong pitch or key could be due to the aforementioned detune or bend range parameters, if they were indeed lost when creating the soundfont. As for "00000052 00081BD8", I'm not actually sure if that's a problem, specifically. I could see that song as being something that plays in an options menu or when paused or something.

Problems with the soundfont -- I don't have much on this. I do intend to look into the soundfont eventually, to see if I can spot anything amiss in it.

No looping -- Yeah, this is not strictly possible, because of short-comings in the MIDI file spec. There's one or two non-standard ways to do looping, but in general they only loop all tracks at once (and generally at the end), while the original songs could do per-track nested looping with specific loop counts. There is actually one (non-standard) way you can do per-track looping, which is to use Apogee's EMIDI extensions that they used for their games in the mid 90s. But even that would require having a MIDI player that understands it.


All that said, I'm still going to keep looking into this. Something that kinda bugs me about the conversion is that it basically just copies the MIDI events verbatim, only handling special cases like the note-on delta time*, meta events, loop points, or the repetition marker (0xFE; never thought I could hate a hex value so much) to get something that resembles a proper MIDI stream. But there's very little checking on the stream, to see if there may be any non-standard controller changes which just get ignored in the playback, or if it may have even re-purposed some standard controllers.

Another thing is that AUDIO.bin has a non-negligible amount of non-sequence data interspersed with the sequence and track data. It may just be junk in unused sections of the file, but I don't know. Considering cartridge limitations and how far even the music goes to save space (MIDI like this is already small enough, but there's cases where the sequence data will use a 4-byte 0xFE repetition marker to "replay" a 6-byte segment), that it seems unbecoming of it to have so much junk in there. But I have a difficult time thinking of what it could be.

* Incidentally, the note-on delta time is something I've seen before in another MIDI-like format (HMI). Instead of having an explicit note-off event, the note-on event specifies how long until release.
Kett
Member
Level: 13


Posts: 16/31
EXP: 9735
For next: 532

Since: 08-07-13


Since last post: 5.1 years
Last activity: 1.5 years
Posted on 11-13-13 04:20:16 PM Link | Quote
Seems like noone bothered to compare the Demo vice files with the final voice files.

I'm currently working on it, there are many altered (or sometimes totally different) files, for example:

The Queen EarthWalker was sick in the final, in the demo, however, she was hurt by the SharpClaw.
The scene would start with Fox instantly asking what happened to Trickys mother, he tells fox about the mushrooms and they go again, no General Pepper or ANY Starfox-related references.
Hugo_Peters

Level: 26


Posts: 41/147
EXP: 99206
For next: 3069

Since: 10-29-13

From: The Netherlands

Since last post: 1.9 years
Last activity: 1.1 years
Posted on 11-13-13 05:04:52 PM (last edited by Hugo_Peters at 11-13-13 06:12:39 PM) Link | Quote
Originally posted by Kett
Seems like noone bothered to compare the Demo vice files with the final voice files.

I'm currently working on it, there are many altered (or sometimes totally different) files, for example:

The Queen EarthWalker was sick in the final, in the demo, however, she was hurt by the SharpClaw.
The scene would start with Fox instantly asking what happened to Trickys mother, he tells fox about the mushrooms and they go again, no General Pepper or ANY Starfox-related references.

Acutally, I just wrote a program yesterday that automatically converts every file to a .wav file. Here is a zip with all 725 voice clips (warning, large file incoming!): https://mega.co.nz/#!rI1XEbIK!TsflXmT76InYX_kgXPPcoz1A5eFQAXTPiB4Kc1I7U0s

I'm currently busy trying to get a GameCube development environment set up, This is what I got so far:
- Dolphin SDK (december 2001)
- Codewarrior for GameCube
- ProDG for GameCube
- MusyX SDK for GameCube
- Some tools and shit

The things above are all mentioned in SFA's code somewhere. It's weird to be working with the same stuff now that they used more than 10 years ago.

EDIT: Finally got the damn thing to compile stuff!!!

____________________
I have a blog: clyck!
puddinpops
Member
Level: 22


Posts: 56/89
EXP: 53996
For next: 4354

Since: 12-27-10


Since last post: 2.4 years
Last activity: 2.2 years
Posted on 11-13-13 10:24:37 PM Link | Quote
Well, after zoinkity's post about this not having any real game code, and the fact we're missing the main EXE, I've lost faith here. I don't know if there's still anything possible here that will change things, so I'm still eying this topic in any case...
nmgschris
User
Level: 8


Posts: 4/10
EXP: 1757
For next: 430

Since: 11-09-13

From: Hanoi, Vietnam

Since last post: 8.4 years
Last activity: 8.1 years
Posted on 11-14-13 12:03:32 AM (last edited by nmgschris at 11-14-13 12:25:03 AM) Link | Quote
Originally posted by puddinpops
Well, after zoinkity's post about this not having any real game code, and the fact we're missing the main EXE, I've lost faith here. I don't know if there's still anything possible here that will change things, so I'm still eying this topic in any case...

if the executable is just a boot program to run the game format then there is still chance to rewrite the code with N64 SDK.
Emoluvjd2
Member
Level: 20


Posts: 60/70
EXP: 39567
For next: 2872

Since: 10-24-09


Since last post: 4.1 years
Last activity: 2.6 years
Posted on 11-14-13 01:21:52 AM (last edited by Emoluvjd2 at 11-14-13 01:22:08 AM) Link | Quote



For whoever plans on making the article for this proto, should I combine the ripped graphics for Diddy Kong Racing 2?
ICEknight
Member
Level: 26


Posts: 55/135
EXP: 97117
For next: 5158

Since: 10-25-11


Since last post: 4.1 years
Last activity: 3.9 years
Posted on 11-14-13 12:34:15 PM (last edited by ICEknight at 11-14-13 12:36:33 PM) Link | Quote
Originally posted by KCat

No looping -- Yeah, this is not strictly possible, because of short-comings in the MIDI file spec. There's one or two non-standard ways to do looping, but in general they only loop all tracks at once (and generally at the end), while the original songs could do per-track nested looping with specific loop counts. There is actually one (non-standard) way you can do per-track looping, which is to use Apogee's EMIDI extensions that they used for their games in the mid 90s. But even that would require having a MIDI player that understands it.

All of the MIDI tracks I've listened to that were extracted from Game Boy Advance games loop perfectly (not just at the end) in Foobar 2000, without tweaking a thing...
oaa
Member
Level: 34


Posts: 234/235
EXP: 236643
For next: 17008

Since: 07-01-10

From: Cleveland

Since last post: 8.3 years
Last activity: 2.5 years
Posted on 11-14-13 02:27:56 PM Link | Quote
Originally posted by Emoluvjd2



For whoever plans on making the article for this proto, should I combine the ripped graphics for Diddy Kong Racing 2?


Should be a subpage
Emoluvjd2
Member
Level: 20


Posts: 61/70
EXP: 39567
For next: 2872

Since: 10-24-09


Since last post: 4.1 years
Last activity: 2.6 years
Posted on 11-15-13 12:20:22 AM Link | Quote
I'm not actually familiar with Diddy Kong Racing, so can someone tell me if some of these textures are specific to the canceled sequel or not?
nmgschris
User
Level: 8


Posts: 5/10
EXP: 1757
For next: 430

Since: 11-09-13

From: Hanoi, Vietnam

Since last post: 8.4 years
Last activity: 8.1 years
Posted on 11-15-13 02:10:00 PM (last edited by nmgschris at 11-15-13 02:13:29 PM) Link | Quote
Originally posted by Emoluvjd2
I'm not actually familiar with Diddy Kong Racing, so can someone tell me if some of these textures are specific to the canceled sequel or not?







The Skybox below look very familiar, and i think they are.

And anyway, i found out that DP appeared to use some kind of DKR & Conker game format mix. So here is my theory, since the offset of both ROM "look very similar" to the one found in DLLS.bin, but i'm still not sure about it but i need to examine it, or even extract the ROM file (although i know it isn't possible), but if it is then i can check out some code or look at the disassembly file (in the case it isn't possible to extract ROM), and then create RawData route host to register and include all contents. Another thing, "System codes", well, i THINK there is a C++ header of the game initialize somewhere in my SDK stuffs, and i believe it was used to initialize the game, but in any case, still need to ask Phil about it. I'm having a problem with the compiler, but i will fix tomorrow.

Note: My friend told me that the waterfx.dll in DLLS.bin seem to be used in Conker's Bad Fur Day, i don't know about it yet but if someone can, go check it out.

If this worked, we might recover the N64 main executable of the ROM, and who know ? Playable state ?

I'll update more.
Hugo_Peters

Level: 26


Posts: 42/147
EXP: 99206
For next: 3069

Since: 10-29-13

From: The Netherlands

Since last post: 1.9 years
Last activity: 1.1 years
Posted on 11-15-13 03:58:17 PM (last edited by Hugo_Peters at 11-15-13 06:35:10 PM) Link | Quote
Originally posted by nmgschris

And anyway, i found out that DP appeared to use some kind of DKR & Conker game format mix. So here is my theory, since the offset of both ROM "look very similar" to the one found in DLLS.bin, but i'm still not sure about it but i need to examine it, or even extract the ROM file (although i know it isn't possible), but if it is then i can check out some code or look at the disassembly file (in the case it isn't possible to extract ROM), and then create RawData route host to register and include all contents. Another thing, "System codes", well, i THINK there is a C++ header of the game initialize somewhere in my SDK stuffs, and i believe it was used to initialize the game, but in any case, still need to ask Phil about it. I'm having a problem with the compiler, but i will fix tomorrow.

Note: My friend told me that the waterfx.dll in DLLS.bin seem to be used in Conker's Bad Fur Day, i don't know about it yet but if someone can, go check it out.

If this worked, we might recover the N64 main executable of the ROM, and who know ? Playable state ?

I'll update more.


I don't want to sound selfish, but I don't want everyone to contact Phil. He's very busy, and I already was lucky to go in depth with him about all this, so I'd suggest I am the "spokesperson" to Phil, as I don't want him to tell everyone the same stuff over and over again.

1. "a" C++ header does not automatically indicate it could be used in any application. I know from Phil that the main executable of DP is not something that goes standard with an SDK, it's the initalization of the game itself, whereafter it gets code from DLLS.bin to swap in and out. For example, DLLS.bin are the wheels of the car, while the main executable would be the motor.

2. You can't extract the ROM. You just... can't. It's compiled code, with compiled binaries in it.

3. I'm pretty sure it doesn't use any code from CBFD, as the code from DP was "directly evolved" from the codebase of Diddy Kong Racing, besides, DP and CBFD were being developed by different teams, and at Rare teams were barely allowed to see each other's games, the company was "incredibly secretive", so, DP format is mix of DKR & CBFD? No. DP format is DKR? Yes,

4. Like I said, this is all compiled already. You can't compile it "again".

[ontopic]
I'm busy porting MuysX from the Dolphin SDK over to libogc. No idea if it will work, but I'm making progress so far!



____________________
I have a blog: clyck!
Peardian

  
Magikoopa

16/3/1: KvSG #479 is up!

Level: 157


Posts: 6940/7597
EXP: 48561389
For next: 1017844

Since: 08-02-07

From: Isle Delfino

Since last post: 1 day
Last activity: 36 min.
Posted on 11-15-13 06:33:18 PM Link | Quote
Originally posted by Emoluvjd2





The sky looks like the exact same one as from Ancient Lake, the first course of the first world. The snowman is from Everfrost Peak, the first course in the snow world. The tree is from Windmill Plains and Greenwood Village, the first two courses of the fourth world.

____________________
-Peardian-
"Kindness is the language which the deaf can hear and the blind can see." -Mark Twain
nmgschris
User
Level: 8


Posts: 6/10
EXP: 1757
For next: 430

Since: 11-09-13

From: Hanoi, Vietnam

Since last post: 8.4 years
Last activity: 8.1 years
Posted on 11-15-13 11:18:31 PM Link | Quote
Originally posted by Hugo_Peters
Originally posted by nmgschris

And anyway, i found out that DP appeared to use some kind of DKR & Conker game format mix. So here is my theory, since the offset of both ROM "look very similar" to the one found in DLLS.bin, but i'm still not sure about it but i need to examine it, or even extract the ROM file (although i know it isn't possible), but if it is then i can check out some code or look at the disassembly file (in the case it isn't possible to extract ROM), and then create RawData route host to register and include all contents. Another thing, "System codes", well, i THINK there is a C++ header of the game initialize somewhere in my SDK stuffs, and i believe it was used to initialize the game, but in any case, still need to ask Phil about it. I'm having a problem with the compiler, but i will fix tomorrow.

Note: My friend told me that the waterfx.dll in DLLS.bin seem to be used in Conker's Bad Fur Day, i don't know about it yet but if someone can, go check it out.

If this worked, we might recover the N64 main executable of the ROM, and who know ? Playable state ?

I'll update more.


I don't want to sound selfish, but I don't want everyone to contact Phil. He's very busy, and I already was lucky to go in depth with him about all this, so I'd suggest I am the "spokesperson" to Phil, as I don't want him to tell everyone the same stuff over and over again.

1. "a" C++ header does not automatically indicate it could be used in any application. I know from Phil that the main executable of DP is not something that goes standard with an SDK, it's the initalization of the game itself, whereafter it gets code from DLLS.bin to swap in and out. For example, DLLS.bin are the wheels of the car, while the main executable would be the motor.

2. You can't extract the ROM. You just... can't. It's compiled code, with compiled binaries in it.

3. I'm pretty sure it doesn't use any code from CBFD, as the code from DP was "directly evolved" from the codebase of Diddy Kong Racing, besides, DP and CBFD were being developed by different teams, and at Rare teams were barely allowed to see each other's games, the company was "incredibly secretive", so, DP format is mix of DKR & CBFD? No. DP format is DKR? Yes,

4. Like I said, this is all compiled already. You can't compile it "again".

[ontopic]
I'm busy porting MuysX from the Dolphin SDK over to libogc. No idea if it will work, but I'm making progress so far!



Sorry for my mistake, i checked the CBFD code again, and you are right, nothing is related.

And i'm mean write a RawData Handle Route and add register to the main R4300i, and include all the contents.

Cow, some guy at Zophar did with 7-Zip, but i'm not sure if it working with all ROMs: http://www.zophar.net/forums/showthread.php?t=13388

And if he too busy then we shouldn't contact with him, at least when he done his project, but not now.
xdaniel
980
Level: 64


Posts: 506/982
EXP: 2151575
For next: 62522

Since: 12-04-08

Pronouns: he/they
From: Germany

Since last post: 16 days
Last activity: 5 hours
Posted on 11-15-13 11:45:33 PM Link | Quote


>>ESTABLISHING LINK...DONE.    >>FETCHING POST DATA...DONE.    >>EXECUTING POSTDISP.BIN...


Originally posted by nmgschris
Cow, some guy at Zophar did with 7-Zip, but i'm not sure if it working with all ROMs: http://www.zophar.net/forums/showthread.php?t=13388

http://jul.rustedlogic.net/thread.php?id=14235


____________________
cu xdaniel -- Follower of the Church of Madoka -- @xdanieldzd (Twitter) -- stapled tech (YouTube)



It doesn't even matter if there is no hope, as the madness of the system grows

Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 ... 33 34 35 36 37 38 39 40 41 42 Next newer thread | Next older thread
Jul - The Cutting Room Floor - Star Fox Adventures E3 2002 prototype (5/17/02) New poll - New thread - New reply


Rusted Logic
Acmlmboard - commit 47be4dc [2021-08-23]
©2000-2022 Acmlm, Xkeeper, Kaito Sinclaire, et al.

34 database queries, 5 query cache hits.
Query execution time:  0.411428 seconds
Script execution time:  0.041930 seconds
Total render time:  0.453359 seconds


TidyHTML vomit below
line 1 column 1 - Warning: missing <!DOCTYPE> declaration
line 119 column 11 - Warning: <form> isn't allowed in <table> elements
line 118 column 10 - Info: <table> previously mentioned
line 120 column 11 - Warning: missing <tr>
line 120 column 119 - Warning: missing </font> before </td>
line 124 column 16 - Warning: plain text isn't allowed in <tr> elements
line 120 column 11 - Info: <tr> previously mentioned
line 125 column 68 - Warning: missing </nobr> before </td>
line 141 column 68 - Warning: missing </nobr> before <tr>
line 147 column 35 - Warning: missing <tr>
line 147 column 50 - Warning: missing </font> before </td>
line 148 column 37 - Warning: unescaped & or unknown entity "&id"
line 147 column 218 - Warning: missing </font> before </table>
line 149 column 35 - Warning: missing <tr>
line 149 column 95 - Warning: unescaped & or unknown entity "&page"
line 149 column 128 - Warning: unescaped & or unknown entity "&page"
line 149 column 161 - Warning: unescaped & or unknown entity "&page"
line 149 column 194 - Warning: unescaped & or unknown entity "&page"
line 149 column 227 - Warning: unescaped & or unknown entity "&page"
line 149 column 260 - Warning: unescaped & or unknown entity "&page"
line 149 column 293 - Warning: unescaped & or unknown entity "&page"
line 149 column 326 - Warning: unescaped & or unknown entity "&page"
line 149 column 359 - Warning: unescaped & or unknown entity "&page"
line 149 column 392 - Warning: unescaped & or unknown entity "&page"
line 149 column 429 - Warning: unescaped & or unknown entity "&page"
line 149 column 464 - Warning: unescaped & or unknown entity "&page"
line 149 column 499 - Warning: unescaped & or unknown entity "&page"
line 149 column 534 - Warning: unescaped & or unknown entity "&page"
line 149 column 573 - Warning: unescaped & or unknown entity "&page"
line 149 column 608 - Warning: unescaped & or unknown entity "&page"
line 149 column 643 - Warning: unescaped & or unknown entity "&page"
line 149 column 678 - Warning: unescaped & or unknown entity "&page"
line 149 column 713 - Warning: unescaped & or unknown entity "&page"
line 149 column 748 - Warning: unescaped & or unknown entity "&page"
line 149 column 783 - Warning: unescaped & or unknown entity "&page"
line 149 column 818 - Warning: unescaped & or unknown entity "&page"
line 149 column 853 - Warning: unescaped & or unknown entity "&page"
line 149 column 888 - Warning: unescaped & or unknown entity "&page"
line 149 column 50 - Warning: missing </font> before </td>
line 149 column 925 - Warning: missing </font> before </table>
line 156 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 158 column 9 - Warning: missing <tr>
line 176 column 13 - Warning: missing <tr>
line 177 column 102 - Warning: unescaped & or unknown entity "&postid"
line 184 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 186 column 9 - Warning: missing <tr>
line 204 column 13 - Warning: missing <tr>
line 205 column 102 - Warning: unescaped & or unknown entity "&postid"
line 219 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 221 column 9 - Warning: missing <tr>
line 239 column 13 - Warning: missing <tr>
line 240 column 102 - Warning: unescaped & or unknown entity "&postid"
line 257 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 259 column 9 - Warning: missing <tr>
line 277 column 13 - Warning: missing <tr>
line 278 column 102 - Warning: unescaped & or unknown entity "&postid"
line 287 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 289 column 9 - Warning: missing <tr>
line 307 column 13 - Warning: missing <tr>
line 308 column 102 - Warning: unescaped & or unknown entity "&postid"
line 318 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 320 column 9 - Warning: missing <tr>
line 338 column 13 - Warning: missing <tr>
line 339 column 102 - Warning: unescaped & or unknown entity "&postid"
line 361 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 363 column 9 - Warning: missing <tr>
line 381 column 13 - Warning: missing <tr>
line 382 column 102 - Warning: unescaped & or unknown entity "&postid"
line 421 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 423 column 9 - Warning: missing <tr>
line 441 column 13 - Warning: missing <tr>
line 442 column 102 - Warning: unescaped & or unknown entity "&postid"
line 452 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 454 column 9 - Warning: missing <tr>
line 472 column 13 - Warning: missing <tr>
line 473 column 102 - Warning: unescaped & or unknown entity "&postid"
line 495 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 497 column 9 - Warning: missing <tr>
line 515 column 13 - Warning: missing <tr>
line 516 column 102 - Warning: unescaped & or unknown entity "&postid"
line 521 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 523 column 9 - Warning: missing <tr>
line 541 column 13 - Warning: missing <tr>
line 542 column 102 - Warning: unescaped & or unknown entity "&postid"
line 548 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 550 column 9 - Warning: missing <tr>
line 568 column 13 - Warning: missing <tr>
line 569 column 102 - Warning: unescaped & or unknown entity "&postid"
line 577 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 579 column 9 - Warning: missing <tr>
line 597 column 13 - Warning: missing <tr>
line 598 column 102 - Warning: unescaped & or unknown entity "&postid"
line 605 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 607 column 9 - Warning: missing <tr>
line 625 column 13 - Warning: missing <tr>
line 626 column 102 - Warning: unescaped & or unknown entity "&postid"
line 636 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 638 column 9 - Warning: missing <tr>
line 656 column 13 - Warning: missing <tr>
line 657 column 102 - Warning: unescaped & or unknown entity "&postid"
line 668 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 670 column 9 - Warning: missing <tr>
line 688 column 13 - Warning: missing <tr>
line 689 column 102 - Warning: unescaped & or unknown entity "&postid"
line 712 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 714 column 9 - Warning: missing <tr>
line 732 column 13 - Warning: missing <tr>
line 733 column 102 - Warning: unescaped & or unknown entity "&postid"
line 761 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 763 column 9 - Warning: missing <tr>
line 781 column 13 - Warning: missing <tr>
line 782 column 102 - Warning: unescaped & or unknown entity "&postid"
line 784 column 74 - Warning: <style> isn't allowed in <td> elements
line 784 column 9 - Info: <td> previously mentioned
line 784 column 363 - Warning: missing </font> before <center>
line 784 column 437 - Warning: inserting implicit <font>
line 784 column 561 - Warning: inserting implicit <font>
line 784 column 561 - Warning: missing </font> before <hr>
line 784 column 627 - Warning: inserting implicit <font>
line 784 column 627 - Warning: missing </font> before <hr>
line 789 column 1 - Warning: inserting implicit <font>
line 797 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 799 column 9 - Warning: missing <tr>
line 817 column 13 - Warning: missing <tr>
line 818 column 102 - Warning: unescaped & or unknown entity "&postid"
line 858 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 860 column 9 - Warning: missing <tr>
line 878 column 13 - Warning: missing <tr>
line 879 column 102 - Warning: unescaped & or unknown entity "&postid"
line 881 column 74 - Warning: <style> isn't allowed in <td> elements
line 881 column 9 - Info: <td> previously mentioned
line 882 column 312 - Warning: missing </div>
line 896 column 17 - Warning: missing <tr>
line 896 column 17 - Warning: discarding unexpected <table>
line 899 column 35 - Warning: missing <tr>
line 899 column 95 - Warning: unescaped & or unknown entity "&page"
line 899 column 128 - Warning: unescaped & or unknown entity "&page"
line 899 column 161 - Warning: unescaped & or unknown entity "&page"
line 899 column 194 - Warning: unescaped & or unknown entity "&page"
line 899 column 227 - Warning: unescaped & or unknown entity "&page"
line 899 column 260 - Warning: unescaped & or unknown entity "&page"
line 899 column 293 - Warning: unescaped & or unknown entity "&page"
line 899 column 326 - Warning: unescaped & or unknown entity "&page"
line 899 column 359 - Warning: unescaped & or unknown entity "&page"
line 899 column 392 - Warning: unescaped & or unknown entity "&page"
line 899 column 429 - Warning: unescaped & or unknown entity "&page"
line 899 column 464 - Warning: unescaped & or unknown entity "&page"
line 899 column 499 - Warning: unescaped & or unknown entity "&page"
line 899 column 534 - Warning: unescaped & or unknown entity "&page"
line 899 column 573 - Warning: unescaped & or unknown entity "&page"
line 899 column 608 - Warning: unescaped & or unknown entity "&page"
line 899 column 643 - Warning: unescaped & or unknown entity "&page"
line 899 column 678 - Warning: unescaped & or unknown entity "&page"
line 899 column 713 - Warning: unescaped & or unknown entity "&page"
line 899 column 748 - Warning: unescaped & or unknown entity "&page"
line 899 column 783 - Warning: unescaped & or unknown entity "&page"
line 899 column 818 - Warning: unescaped & or unknown entity "&page"
line 899 column 853 - Warning: unescaped & or unknown entity "&page"
line 899 column 888 - Warning: unescaped & or unknown entity "&page"
line 899 column 50 - Warning: missing </font> before </td>
line 899 column 925 - Warning: missing </font> before </table>
line 901 column 35 - Warning: missing <tr>
line 901 column 50 - Warning: missing </font> before </td>
line 902 column 37 - Warning: unescaped & or unknown entity "&id"
line 901 column 218 - Warning: missing </font> before </table>
line 903 column 17 - Warning: discarding unexpected </textarea>
line 903 column 28 - Warning: discarding unexpected </form>
line 903 column 35 - Warning: discarding unexpected </embed>
line 903 column 43 - Warning: discarding unexpected </noembed>
line 903 column 53 - Warning: discarding unexpected </noscript>
line 903 column 64 - Warning: discarding unexpected </noembed>
line 903 column 74 - Warning: discarding unexpected </embed>
line 903 column 82 - Warning: discarding unexpected </table>
line 903 column 90 - Warning: discarding unexpected </table>
line 905 column 9 - Warning: missing </font> before <table>
line 917 column 25 - Warning: discarding unexpected </font>
line 926 column 57 - Warning: discarding unexpected </font>
line 904 column 1 - Warning: missing </center>
line 120 column 63 - Warning: <img> lacks "alt" attribute
line 125 column 19 - Warning: <td> attribute "width" has invalid value "120px"
line 125 column 93 - Warning: <img> lacks "alt" attribute
line 141 column 19 - Warning: <td> attribute "width" has invalid value "120px"
line 141 column 98 - Warning: <img> lacks "alt" attribute
line 148 column 44 - Warning: <img> proprietary attribute value "absmiddle"
line 148 column 142 - Warning: <img> proprietary attribute value "absmiddle"
line 148 column 246 - Warning: <img> proprietary attribute value "absmiddle"
line 161 column 21 - Warning: <img> lacks "alt" attribute
line 161 column 62 - Warning: <img> lacks "alt" attribute
line 161 column 111 - Warning: <img> lacks "alt" attribute
line 161 column 161 - Warning: <img> lacks "alt" attribute
line 172 column 15 - Warning: <img> lacks "alt" attribute
line 176 column 92 - Warning: <font> attribute "color" had invalid value "97ACEF" and has been replaced
line 189 column 22 - Warning: <img> lacks "alt" attribute
line 189 column 63 - Warning: <img> lacks "alt" attribute
line 189 column 112 - Warning: <img> lacks "alt" attribute
line 189 column 162 - Warning: <img> lacks "alt" attribute
line 200 column 15 - Warning: <img> lacks "alt" attribute
line 224 column 22 - Warning: <img> lacks "alt" attribute
line 224 column 63 - Warning: <img> lacks "alt" attribute
line 224 column 112 - Warning: <img> lacks "alt" attribute
line 224 column 162 - Warning: <img> lacks "alt" attribute
line 225 column 11 - Warning: <img> lacks "alt" attribute
line 235 column 15 - Warning: <img> lacks "alt" attribute
line 262 column 21 - Warning: <img> lacks "alt" attribute
line 262 column 62 - Warning: <img> lacks "alt" attribute
line 262 column 111 - Warning: <img> lacks "alt" attribute
line 262 column 161 - Warning: <img> lacks "alt" attribute
line 273 column 15 - Warning: <img> lacks "alt" attribute
line 292 column 22 - Warning: <img> lacks "alt" attribute
line 292 column 63 - Warning: <img> lacks "alt" attribute
line 292 column 112 - Warning: <img> lacks "alt" attribute
line 292 column 162 - Warning: <img> lacks "alt" attribute
line 293 column 11 - Warning: <img> lacks "alt" attribute
line 303 column 15 - Warning: <img> lacks "alt" attribute
line 323 column 21 - Warning: <img> lacks "alt" attribute
line 323 column 62 - Warning: <img> lacks "alt" attribute
line 323 column 111 - Warning: <img> lacks "alt" attribute
line 323 column 161 - Warning: <img> lacks "alt" attribute
line 334 column 15 - Warning: <img> lacks "alt" attribute
line 338 column 92 - Warning: <font> attribute "color" had invalid value "97ACEF" and has been replaced
line 366 column 22 - Warning: <img> lacks "alt" attribute
line 366 column 63 - Warning: <img> lacks "alt" attribute
line 366 column 112 - Warning: <img> lacks "alt" attribute
line 366 column 162 - Warning: <img> lacks "alt" attribute
line 377 column 15 - Warning: <img> lacks "alt" attribute
line 381 column 92 - Warning: <font> attribute "color" had invalid value "7C60B0" and has been replaced
line 426 column 22 - Warning: <img> lacks "alt" attribute
line 426 column 63 - Warning: <img> lacks "alt" attribute
line 426 column 112 - Warning: <img> lacks "alt" attribute
line 426 column 162 - Warning: <img> lacks "alt" attribute
line 437 column 15 - Warning: <img> lacks "alt" attribute
line 457 column 22 - Warning: <img> lacks "alt" attribute
line 457 column 63 - Warning: <img> lacks "alt" attribute
line 457 column 112 - Warning: <img> lacks "alt" attribute
line 457 column 162 - Warning: <img> lacks "alt" attribute
line 458 column 11 - Warning: <img> lacks "alt" attribute
line 468 column 15 - Warning: <img> lacks "alt" attribute
line 472 column 92 - Warning: <font> attribute "color" had invalid value "97ACEF" and has been replaced
line 500 column 22 - Warning: <img> lacks "alt" attribute
line 500 column 63 - Warning: <img> lacks "alt" attribute
line 500 column 112 - Warning: <img> lacks "alt" attribute
line 500 column 162 - Warning: <img> lacks "alt" attribute
line 511 column 15 - Warning: <img> lacks "alt" attribute
line 526 column 21 - Warning: <img> lacks "alt" attribute
line 526 column 62 - Warning: <img> lacks "alt" attribute
line 526 column 111 - Warning: <img> lacks "alt" attribute
line 526 column 161 - Warning: <img> lacks "alt" attribute
line 537 column 15 - Warning: <img> lacks "alt" attribute
line 541 column 92 - Warning: <font> attribute "color" had invalid value "97ACEF" and has been replaced
line 553 column 22 - Warning: <img> lacks "alt" attribute
line 553 column 63 - Warning: <img> lacks "alt" attribute
line 553 column 112 - Warning: <img> lacks "alt" attribute
line 553 column 162 - Warning: <img> lacks "alt" attribute
line 554 column 11 - Warning: <img> lacks "alt" attribute
line 564 column 15 - Warning: <img> lacks "alt" attribute
line 568 column 92 - Warning: <font> attribute "color" had invalid value "7C60B0" and has been replaced
line 572 column 78 - Warning: <img> lacks "alt" attribute
line 582 column 22 - Warning: <img> lacks "alt" attribute
line 582 column 63 - Warning: <img> lacks "alt" attribute
line 582 column 112 - Warning: <img> lacks "alt" attribute
line 582 column 162 - Warning: <img> lacks "alt" attribute
line 593 column 15 - Warning: <img> lacks "alt" attribute
line 597 column 92 - Warning: <font> attribute "color" had invalid value "7C60B0" and has been replaced
line 610 column 22 - Warning: <img> lacks "alt" attribute
line 610 column 63 - Warning: <img> lacks "alt" attribute
line 610 column 112 - Warning: <img> lacks "alt" attribute
line 610 column 162 - Warning: <img> lacks "alt" attribute
line 611 column 11 - Warning: <img> lacks "alt" attribute
line 621 column 15 - Warning: <img> lacks "alt" attribute
line 629 column 156 - Warning: <img> lacks "alt" attribute
line 641 column 22 - Warning: <img> lacks "alt" attribute
line 641 column 63 - Warning: <img> lacks "alt" attribute
line 641 column 112 - Warning: <img> lacks "alt" attribute
line 641 column 162 - Warning: <img> lacks "alt" attribute
line 642 column 11 - Warning: <img> lacks "alt" attribute
line 652 column 15 - Warning: <img> lacks "alt" attribute
line 661 column 225 - Warning: <img> lacks "alt" attribute
line 663 column 288 - Warning: <img> lacks "alt" attribute
line 665 column 351 - Warning: <img> lacks "alt" attribute
line 673 column 21 - Warning: <img> lacks "alt" attribute
line 673 column 62 - Warning: <img> lacks "alt" attribute
line 673 column 111 - Warning: <img> lacks "alt" attribute
line 673 column 161 - Warning: <img> lacks "alt" attribute
line 684 column 15 - Warning: <img> lacks "alt" attribute
line 688 column 92 - Warning: <font> attribute "color" had invalid value "97ACEF" and has been replaced
line 693 column 303 - Warning: <img> lacks "alt" attribute
line 695 column 366 - Warning: <img> lacks "alt" attribute
line 697 column 429 - Warning: <img> lacks "alt" attribute
line 717 column 22 - Warning: <img> lacks "alt" attribute
line 717 column 63 - Warning: <img> lacks "alt" attribute
line 717 column 112 - Warning: <img> lacks "alt" attribute
line 717 column 162 - Warning: <img> lacks "alt" attribute
line 718 column 11 - Warning: <img> lacks "alt" attribute
line 728 column 15 - Warning: <img> lacks "alt" attribute
line 732 column 92 - Warning: <font> attribute "color" had invalid value "97ACEF" and has been replaced
line 758 column 2650 - Warning: <img> lacks "alt" attribute
line 765 column 17 - Warning: <img> lacks "alt" attribute
line 766 column 23 - Warning: <img> lacks "alt" attribute
line 766 column 64 - Warning: <img> lacks "alt" attribute
line 766 column 112 - Warning: <img> lacks "alt" attribute
line 766 column 162 - Warning: <img> lacks "alt" attribute
line 767 column 11 - Warning: <img> lacks "alt" attribute
line 777 column 15 - Warning: <img> lacks "alt" attribute
line 784 column 437 - Warning: <img> lacks "alt" attribute
line 784 column 627 - Warning: <img> lacks "alt" attribute
line 786 column 690 - Warning: <img> lacks "alt" attribute
line 788 column 753 - Warning: <img> lacks "alt" attribute
line 792 column 1504 - Warning: <img> lacks "alt" attribute
line 802 column 21 - Warning: <img> lacks "alt" attribute
line 802 column 62 - Warning: <img> lacks "alt" attribute
line 802 column 111 - Warning: <img> lacks "alt" attribute
line 802 column 161 - Warning: <img> lacks "alt" attribute
line 813 column 15 - Warning: <img> lacks "alt" attribute
line 843 column 2730 - Warning: <img> lacks "alt" attribute
line 862 column 15 - Warning: <img> proprietary attribute value "absmiddle"
line 862 column 15 - Warning: <img> lacks "alt" attribute
line 862 column 58 - Warning: <img> proprietary attribute value "absmiddle"
line 862 column 58 - Warning: <img> lacks "alt" attribute
line 862 column 101 - Warning: <img> proprietary attribute value "absmiddle"
line 862 column 101 - Warning: <img> lacks "alt" attribute
line 862 column 144 - Warning: <img> proprietary attribute value "absmiddle"
line 862 column 144 - Warning: <img> lacks "alt" attribute
line 862 column 187 - Warning: <img> proprietary attribute value "absmiddle"
line 862 column 187 - Warning: <img> lacks "alt" attribute
line 862 column 230 - Warning: <img> proprietary attribute value "absmiddle"
line 862 column 230 - Warning: <img> lacks "alt" attribute
line 862 column 273 - Warning: <img> proprietary attribute value "absmiddle"
line 862 column 273 - Warning: <img> lacks "alt" attribute
line 862 column 316 - Warning: <img> proprietary attribute value "absmiddle"
line 862 column 316 - Warning: <img> lacks "alt" attribute
line 862 column 359 - Warning: <img> proprietary attribute value "absmiddle"
line 862 column 359 - Warning: <img> lacks "alt" attribute
line 862 column 402 - Warning: <img> proprietary attribute value "absmiddle"
line 862 column 402 - Warning: <img> lacks "alt" attribute
line 863 column 22 - Warning: <img> lacks "alt" attribute
line 863 column 63 - Warning: <img> lacks "alt" attribute
line 863 column 112 - Warning: <img> lacks "alt" attribute
line 863 column 162 - Warning: <img> lacks "alt" attribute
line 864 column 11 - Warning: <img> lacks "alt" attribute
line 874 column 15 - Warning: <img> lacks "alt" attribute
line 888 column 991 - Warning: <div> anchor "divxdn" already defined
line 890 column 1308 - Warning: <img> lacks "alt" attribute
line 890 column 1443 - Warning: <img> lacks "alt" attribute
line 902 column 44 - Warning: <img> proprietary attribute value "absmiddle"
line 902 column 142 - Warning: <img> proprietary attribute value "absmiddle"
line 902 column 246 - Warning: <img> proprietary attribute value "absmiddle"
line 911 column 25 - Warning: <img> lacks "alt" attribute
line 916 column 267 - Warning: <img> lacks "alt" attribute
line 784 column 363 - Warning: trimming empty <font>
line 896 column 17 - Warning: trimming empty <tr>
line 125 column 68 - Warning: <nobr> is not approved by W3C
line 141 column 68 - Warning: <nobr> is not approved by W3C
line 177 column 27 - Warning: <nobr> is not approved by W3C
line 205 column 27 - Warning: <nobr> is not approved by W3C
line 240 column 27 - Warning: <nobr> is not approved by W3C
line 278 column 27 - Warning: <nobr> is not approved by W3C
line 308 column 27 - Warning: <nobr> is not approved by W3C
line 339 column 27 - Warning: <nobr> is not approved by W3C
line 382 column 27 - Warning: <nobr> is not approved by W3C
line 442 column 27 - Warning: <nobr> is not approved by W3C
line 473 column 27 - Warning: <nobr> is not approved by W3C
line 516 column 27 - Warning: <nobr> is not approved by W3C
line 542 column 27 - Warning: <nobr> is not approved by W3C
line 569 column 27 - Warning: <nobr> is not approved by W3C
line 598 column 27 - Warning: <nobr> is not approved by W3C
line 626 column 27 - Warning: <nobr> is not approved by W3C
line 657 column 27 - Warning: <nobr> is not approved by W3C
line 689 column 27 - Warning: <nobr> is not approved by W3C
line 733 column 27 - Warning: <nobr> is not approved by W3C
line 782 column 27 - Warning: <nobr> is not approved by W3C
line 791 column 1167 - Warning: <td> proprietary attribute "background"
line 818 column 27 - Warning: <nobr> is not approved by W3C
line 879 column 27 - Warning: <nobr> is not approved by W3C
Info: Document content looks like HTML5
Info: No system identifier in emitted doctype
Tidy found 369 warnings and 0 errors!


The alt attribute should be used to give a short description
of an image; longer descriptions should be given with the
longdesc attribute which takes a URL linked to the description.
These measures are needed for people using non-graphical browsers.

For further advice on how to make your pages accessible
see http://www.w3.org/WAI/GL.
You are recommended to use CSS to specify the font and
properties such as its size and color. This will reduce
the size of HTML files and make them easier to maintain
compared with using <FONT> elements.

You are recommended to use CSS to control line wrapping.
Use "white-space: nowrap" to inhibit wrapping in place
of inserting <NOBR>...</NOBR> into the markup.

About HTML Tidy: https://github.com/htacg/tidy-html5
Bug reports and comments: https://github.com/htacg/tidy-html5/issues
Official mailing list: https://lists.w3.org/Archives/Public/public-htacg/
Latest HTML specification: http://dev.w3.org/html5/spec-author-view/
Validate your HTML documents: http://validator.w3.org/nu/
Lobby your company to join the W3C: http://www.w3.org/Consortium

Do you speak a language other than English, or a different variant of
English? Consider helping us to localize HTML Tidy. For details please see
https://github.com/htacg/tidy-html5/blob/master/README/LOCALIZE.md