Access errors and page shells

Saved AW-NET responses show where access stopped, and how frames separated a page's layout from its contents.

Some saved addresses lead to an error message, a handset restriction or a frame container. Their filenames can resemble help pages, shops or player records even when that content was not returned. This page brings those responses together and preserves the individual files below. The interface record covers login fields, ranking menus and navigation.

Capture dates describe the archived responses, not the dates on which a feature launched or an error began. “Original HTML as text” opens the preserved response bytes; a raw file's relative links may depend on files that were saved separately.

Salaryman Kintaro: registration and online-play errors

Sixteen captures show the heading AW-NET ERROR and this instruction:

カード登録・オンライン筐体でのプレイ後、再度ご利用下さい。

English: After registering your card and playing on an online cabinet, please try again.

The seventeenth, the event-control response saved on 11 September 2004, says:

現在ＡＷカードが登録されていません。ＡＷカードの登録後、再度ご利用下さい。

English: An AW card is not currently registered. Please try again after registering one.

These messages document an access requirement shown to the requesting session. They do not reveal the requested help, shop, event, statistics or personal-record content, and they do not establish the state of any particular historical player's account. All 17 responses link back to Kintaro and AW-NET top pages. Several have identical bytes; different addresses and capture times remain separate provenance entries.

The routes below are relative to http://www.awnet.jp:80/ns_kintaro/cgi-bin/.

AW GGX Mobile: unsupported-handset response

Both saved responses say 非対応端末です (“Unsupported handset”) and explain that the model being used cannot access the service. They do not identify a handset model or provide the supported-model list. The same bytes were saved at the main AW-NET address in September 2003 and the mobile address in November 2003; the addresses and dates are both worth preserving.

AW-NET's missing-page message

The saved /pc/_error.html response says the requested page could not be found, and lists deletion, a changed address or temporary unavailability as possible explanations. Its text and HTML refresh directive return the visitor to index.html after 10 seconds. This is evidence of the site's error interface; it does not establish which explanation applied or the original HTTP status code.

Page shells and browser fallbacks

These ten files are normal layout evidence, rather than recovered article text. A frameset loads other documents into named regions; an iframe embeds another document inside the page. A text extractor can expose only the fallback message or empty body tags while missing the separately loaded content.

The February 2004 AW-NET front page loads head.html and content_frame.html. The December 2003 Isuka demo shell loads menu.cgi and top.html. Furlong's November–December 2004 shells combine a menu, top strip, main page and footer. The AW-NET main-page captures embed text.html for news and offer that same address to browsers without iframe support.

The table retains real layout differences: Furlong's menu filename and bottom-row height change, and AW-NET's news iframe grows between the June and November captures. The fallback text is not a substitute for the news or game pages. The reconstructed AW-NET site offers assembled browsing; it combines preserved material and is not an exact replay of every capture listed here. Other restored sites are listed under Original websites.

The original files remain available even where two captures share identical bytes. No help text, player record, shop inventory or missing frame content has been invented to fill these gaps.