AW-NET website interface

Surviving forms and menus show how visitors logged in, selected rankings and reached game services.

These fragments preserve the website's controls and navigation. They are useful for understanding and reconstructing its interface, even when a capture contains no player records or ranking results. Each source file is linked below, with its original requested address and capture time. Access errors and page shells explains the related registration failures, handset restrictions and frame layout.

AW-NET sidebar: login and navigation

The twelve saved /pc/menu.cgi responses contain an AWID text field, a password field and a login button. The form posts back to menu.cgi. The early captures use many image-based links, so extracting only text reduces a substantial sidebar to its notice that parts of the site require Flash Player. The original HTML's image labels and link destinations preserve more of the menu.

Across the captures, the sidebar links to service information, games, FAQs, inquiries and events. Later versions also expose notices, ranking charts and competition results as text links. The 26 January 2005 capture links to the first two Ring Battle results and first three Fight Money results. The 3 March 2005 capture adds a Furlong coming-soon notice and the third Ring Battle result link. A navigation link alone does not prove that its destination's content was captured or that a service was already available.

One provenance exception matters: the request dated 14 January 2005 resolved to a 16 January replay. The stored body matches the requested capture's recorded digest, but those are different timestamps. Both appear below. None of these saved forms provides a working historical login service.

Salaryman Kintaro: ranking selection

Five responses saved on 15 April 2004 preserve the same visible ranking choices and navigation. They contain menus, not recovered lists of ranked players. The HTML submits each category to its own ranking route; some responses also preserve previous/next-page forms.

Menu	Choices shown in the source
Overall	Overall ranking, area ranking, overall monthly performance
Three-player mahjong	Dan rank, three-player mahjong ranking, monthly three-player mahjong ranking, Yakuman King, Dora King
Daifugo	Dan rank, performance, monthly performance, Daifugo King, Revolution King
Reversi	Dan rank, performance, monthly performance, Stone King, Perfect King, White King, Black King

These are translations of menu labels. They do not reconstruct the scoring or aggregation rules. The common navigation offers Top, Personal information, Databank, Rankings, Events, AW Shop, Help and Login. The separate Kintaro access-error captures show why a saved service address should not automatically be treated as recovered member content.

Guilty Gear Isuka: ranking navigation

Two captures of /pc/ggi/ranking.html preserve six sets of links, labelled overall, Holy Order and Bounty rankings. The source also tells visitors to enable JavaScript and cookies. These are category controls, rather than result tables; surviving results are collected with the Isuka leaderboards.

For reconstruction, one detail should remain visible: the third link to ranking03.cgi uses mod=3 in both captures, whereas the third link in the other five sets uses mod=2. The files preserve that difference; the menu alone does not establish how the server handled it.

Battle Coliseum: location-test My Data prompt

The 7 May 2005 response asks for the USER ACCESS CODE from a location-test AW card to view play information. It shows four text fields, each limited to four characters, and a confirmation button. The form sends a myview request. This is the entry prompt, not a recovered player's My Data screen; the fields are text inputs, not proof of numeric-only browser validation.

Logout confirmation

The 29 May 2004 /pc/log_out.cgi response presents a logout-complete message and thanks the visitor for using the member site. Its text and refresh directive return to index.html after 10 seconds. The preserved confirmation page documents the interface; it does not prove an authenticated session was captured.

For assembled browsing, visit the reconstructed AW-NET site. Its combined interface is distinct from the individual dated responses preserved here.