modelrail.otenko

26Jul/150

Osaka Freight: Suita to Ajikawaguchi (Super Rail Cargo)

This line is an extension of the Suita to Umeda freight/express-train line that runs from Shin-Osaka Station to the Umeda Freight Yards.

This line continues further south-west, rising back up to the height of the kanjosen and then branching off on the Yumesaki Line to Universal Studios Japan. Before this though, is Ajikawaguchi freight yards. The home of Sagawa Transport's M250!

This freight train is famous... it's actually an EMU high-speed express freight service that runs through the night to get your urgent deliveries to Tokyo. The opposing service departs Tokyo at the same time and they pass somewhere half-way along the Tokaido Main Line in the middle of the night.

Due to its timetable, you'll really only ever see it resting in the Ajikawaguchi yard. Sometimes I've seen it photographed in the early morning at the Tokyo end, but never really in daylight when moving.

Due to this, I still haven't managed to properly photograph this train. I've seen it depart Ajikawaguchi once and you can find a post with a movie of the departure over here.

Rail-set Train

The last column on each table is a rail-set train. I've seen this pass before from an assortment of locations.

Ajikawaguchi

This area is difficult to photograph, but there is a large level crossing on which you can gently walk into the middle of and take photos. Just be very considerate and respect the requests of staff if they ask you to get out of the way!

Timetables

As per previous Osaka timetables, all times are up until Suita. I'll look into extending the SRC through to Tokyo at a later date.

Service	Origin	Arrive	Depart	Arrive	Comments
Southbound		Suita		Ajikawaguchi
▲51	Tokyo	––	0511	0526	▲ = 日曜日運休 (Not Sundays)
▲59	Tokyo	––	0451	0510	▲ = 土 or 休日運休 (Not Saturdays or Holidays)
(4078) ~ (1081) ~ 91	Sendai	ºº0723	0833	0900	ºº = ??
▲93	Osaka	1102	1111	1157	▲ = 月曜日運休 (Not Mondays)
(1881) ~ 1883	Kyoto	1447	1603	1628	Rail-set or 'other' cargo.

Service	Depart	Arrive	Depart	Destination	Comments
Northbound	Ajikawaguchi	Suita
▲50	2309	––	2324	Tokyo	▲ = 日曜日運休 (Not Sundays)
▲58	2259	2320	2328	Tokyo	▲ = 土 or 休日運休 (Not Saturdays or Holidays)
▲90	1703	1739	1742	Osaka	▲ = 日曜日運休 (Not Sundays)
5088 ~ (3089)	1818	ºº1851	1944	Sendai	ºº = ??
1180 ~ (1182)	1040	ºº1127	1225	Kyoto	ºº = ?? Rail train or 'other' cargo.

I will go back and get the Super Rail Cargo once more!

No Comments

26Jul/150

Osaka Freight: Suita to Umeda Freight Terminal

REALLY BIG UPDATE: As of ... god knows when ... this yard has been entirely removed! Here I was, 2 weeks ago, at Shin Osaka station, waiting for a train from Umeda to pass but, alas, nothing came through. Turns out that, upon cruising past on the Haruka, the Umeda Freight Yards no longer exist! The timetables below are still valid but all traffic terminates at Suita.

Any mention of Umeda below is historical. The timetables have been updated to show Osaka... This yard is located right next to the Shinkansen Depot to the south-east of Senrioka.

Buried in upper-central Osaka is Umeda, home of the Hep-5 ferris wheel, the Umeda Sky building, the amazingly-new Osaka station and a relic: The Umeda Freight yards. Very easy to access, these yards' time has to be limited. The yard is situated on a prime development location and the surrounding buildings have slowly been creeping in.

In the yard you'll usually find any number of EF66s, EF81s, EF210s and DE10s for the shunting. There was a rake of WAMUs in there when I checked it out 10years ago, but recently it's been only container traffic. There is a large shed at the southern end which restricts visibility. You'll also find a very long passenger tunnel under the width of the yard. It connects the Umeda Sky Building to Yodobashi Camera. I really do wish this was an overpass!

I'd previously walked around the area and took a few photographs. The album is here if you want to check it out.

This yard is on the 'Osaka Station Bypass' that the high-speed trains to Wakayama and the Airport use. Also the Super Rail Cargo to Ajikawaguchi and the freight trains I'll mention in this post.

The traffic mentioned is fun to photograph and the lighting at any time of day provides great opportunities. Below are some shots of the area. Note that the first photo below was taken from the Heart-Inn hotel just south of the yard and walking distance from Osaka Station.

Timetables

Times listed are between Suita and Osaka and don't relate to the map above :) I'll update that soon!

Service	Origin	Arrive	Depart	Arrive	Comments
Southbound		Suita		Osaka
1069	Niiza	0616	0656	0705
3050	Fukuoka	0721	0742	0754
▲4058	Niigata	0654	0732	0741	▲ = 休日運休 (Not Holidays)
(2060) ~ 4060	Sapporo	2026	2054	2103
▲5066	Hiroshima	ºº1446	1533	1545	▲ = 火曜日運休 (Not Tuesdays) Has ºº, define this.
▲56	Tosu	0506	0516	0528	▲ = 日曜日運休 (Not Sundays)
(3072) ~ 72	Matsuyama	1002	1034	1045
(3076) ~ 76	Niihama	0329	0433	0445
84	Hirano	1700	1705	1717
86	Himeji	ºº1747	1838	1850	(Timetable has ºº. Define this.)
▲90	Ajikawaguchi	1739	1742	1754	▲ = 日曜日運休 (Not Sundays)
(4088) ~ 1085	Sendai	0458	0536	0545
1089	Tokyo	0527	0605	0614
2074	Kagoshima	ºº1248	1319	1330	(Timetable has ºº. Define this.)
3094	Kanazawa	0430	0508	0517
8098	Aomori	0039	0422	0433
1392	Hirano	1459	1501	1515	配給 = Light Engine Movement
1476	Suita	––	0926	0937	配給 = Light Engine Movement

Service	Depart	Arrive	Depart	Destination	Comments
Northbound	Osaka	Suita
▲57	2043	2056	2058	Tosu	▲ = 日曜日運休 (Not Sundays)
1066	2024	2033	2117	Tokyo
▲4059	2232	2241	2319	Niigata	▲ = 休日運休 (Not Holidays)
4061	2324	2333	0011	Sapporo
73	0824	0836	0848	Takamatsu
75	1547	1600	1630	Takamatsu
81	1112	1124	1126	Himeji
83	1124	1138	1212	Hirano
85	2105	2117	2127	Himeji
▲93	1049	1102	1111	Ajikawaguchi	▲ = 月曜日運休 (Not Mondays)
▲1080	1924	1934	2017	Niiza	▲ = 日曜日運休 (Not Sundays)
1084 ~ (4089)	1829	1839	1925	Sendai
▲2081	1230	1243	1256	Fukuoka	▲ = 月曜日運休 (Not Mondays)
2089	1211	1224	1226	Okayama
3095	1333	1343	1425	Kanazawa
62 ~ (3051)	1640	ºº1651	2029	Fukuoka	Define ºº on stop at Suita.

All traffic above is containerised. Also note that the yard can only be entered from the north. Hence trains to Ajikawaguchi (which is further down the line) have to be accessed by running around at Suita!

No Comments

24Jul/150

WCF Clients: Set credentials BEFORE you do anything else!

I've just lost hours of my time and, Microsoft, I'd love it back. I had HTTPS WCF services running from a web app on IIS and I needed to merge in a NET.TCP service as well. Web.config hell, I tell you, but it eventually worked.

I then tried to set the ASP.NET Membership Authentication 'required' on the push services (DuplexChannelFactory) via NET.TCP. Everything I read online said I needed a certificate, so I specified this on the server, using the server certificate as I already had HTTPS configured.

This all worked OK... but trying to specify the Username and Password on the channel factory for the generated Client was a nightmare!

It turns out that, long story short, you SHOULD NOT do anything to the generated client after instantiating it. Set the username and password immediately.

This will work:

WcfClient = new WcfClient (new InstanceContext(WcfCallback), "");
WcfClient.ChannelFactory.Credentials.UserName.UserName = "username";
WcfClient.ChannelFactory.Credentials.UserName.Password = "password";
WcfClient.InnerChannel.Opened += WcfClient_Opened;

This wont:

WcfClient = new WcfClient (new InstanceContext(WcfCallback), "");
WcfClient.InnerChannel.Opened += WcfClient_Opened;
WcfClient.ChannelFactory.Credentials.UserName.UserName = "username";
WcfClient.ChannelFactory.Credentials.UserName.Password = "password";

Adding events to the ChannelFactory worked OK, if done prior to the credential configuration. But as soon as you touch the InnerChannel it'll throw a read-only exception as follows:

InvalidOperationException was caught
Object is read-only.

Anyway, the re-ordering worked like a charm... just keep an eye on it!

No Comments

24Jul/150

Osaka Freight: Suita to Hirano (Kudara Terminal)

There are three ways for freight to be delivered into Osaka by rail. The first is into Ajikawaguchi located to the west of the city near Universal Studios, The second is into Umeda Freight Terminal, right in the heart next to Osaka Station, and the third is to take the Osaka Higashi Line to the east and arrive at Hirano Station. The latter service is the one we'll be investigating today.

The freight line itself runs south out of Suita Terminal, over the Yodogawa (Yodo River) and then wraps around the city, clockwise from Shigino to Hirano. This used to be freight only, or for movements to dead-head electric stock, but it currently being upgraded to a passenger line. The line was originally to be called the 'Osaka Outer Loop Line', but is now to be known as the Osaka Higashi Line. At Suita, the freight approaches from Suita in the east, whereas the passenger services will approach from Shin-Osaka in the west. Likewise, at the end of the line the passenger services will take the triangle to the west and arrive at Shinkami/Kyuhoji, whereas the freight ventures west to Hirano Freight Yard.

Currently there is no passenger service between Shigino and Shin-Osaka, but this is expected to start by 2018. There seems to have been an illegal site occupation on the former alignment near the triangle at Suita.

Seen to the left is the map of the line from both Google and Yahoo respectively. As you can see, the blue line highlights the path which crosses the river and then heads around lower Osaka.

There are no yards in between Suita and Hirano, so the freight will proceed as quickly as possible south, slotting in to the passenger traffic at the junction north of Shigino.

Once at Hirano, the freight is transferred to road vehicles for the rest of the journey.

I believe that both electic and diesel locomotives work over this line, but I've only currently seen DD51s pulling the freight services. Then again, if you look at the an EF66 here on Street View and an EF81. That latter EF81 looks like the locomotive I photographed in Umeda Yard years ago.

Timetables

Thanks to the latest JR Freight Timetable for 2015, I can provide the following timings for the freight services in and out of Hirano. Please do take note of the comments column and ensure that you're ready for disappointment. Not all services run on this line, regardless of the slots available.

Service	Origin	Arrive	Depart	Arrive	Comments
Southbound		Suita		Hirano
▲65	Tokyo	0542	0547	0623	▲ = 日曜日運休 (Not Sundays)
1067	Koshigaya	0442	0444	0515
83	Osaka	1138	1212	1251
(▲1077) ~ ▲1079	Niiza	0948	1145	1222	▲ = 新座(夕)-横浜羽沢間稲沢-百済(夕)間日曜日運休 (Not Sundays between Niiza[Evenings]-Yokohama and Inazawwa-Hirano[Evenings])
▲1092	Nabeshima	1311	1350	1422	▲ = 日曜日運休 (Not Sundays)
▲4070	Niigata	0625	0637	0719	▲ = 南長岡-百済(夕)間休日運休 (Not Holidays between South Nagaoka-Hirano[Evenings])
(▲4077) ~ ▲4076	Hachinohe	1647	1713	1748	▲ = 日曜日運休 (Not Sundays)
(82) ~ (▲3082) ~ ▲5087	Asahikawa	1420	1422	1453	▲ = 青森(信)-百済(夕)間月曜日運休 (Not Mondays between Aomori[Junction]-Hirano[Evenings])
¤7085	Tokyo	0411	0420	0457	¤ = Runs on unknown dates, not regularly.
8096	Sapporo	1352	1404	1440

Service	Depart	Arrive	Depart	Destination	Comments
Northbound	Hirano	Suita
▲64	2129	2201	2232	Tokyo	▲ = 日曜日運休 (Not Sundays)
84	1629	1700	1705	Osaka
▲1074 ~ (1076)	1945	2018	2044	Niiza	▲ = 百済(夕)-稲沢間日曜日運休 (Not Sundays between Inazawwa[Evenings]-Hirano)
1078	2044	2144	2128	Koshigaya
▲1093	1929	2002	2043	Fukuoka	▲ = 日曜日運休 (Not Sundays)
▲4071	1303	1335	1427	Niigata	▲ = 休日運休 (Not Holidays)
▲4075 ~ (▲4074)	1959	2030	2123	Aomori	▲ = 日曜日運休 (Not Sundays)
▲5086 ~ (▲3083) ~ (83)	2231	2304	2312	Sapporo	▲ = 百済(夕)-青森(信)間日曜日運休 (Not Mondays between Hirano[Evenings]-Aomori[Junction])
¤7082	2150	2222	2240	Tokyo	¤ = Runs on unknown dates, not regularly.
8097	2307	2342	0140	Sapporo
1392	1425	1459	1501	Osaka	配給 = Light Engine Movement

I've translated the comments from the timetable to the best of my ability. From this I've even learnt of new freight yards that I had no idea about. For the comments that also suggest places, I'm a little confused... Should there be a need to state the to/from, when you could just say that the service doesn't run? Or is it part of a greater service where some legs aren't always operating? Does this mean that the consists will be shorter?

I'll find out in a few weeks when I go stalk this service for a morning or two!

No Comments

19Jul/151

DE10 Locomotive – Co-Bo or AAA-B?

Any idea what I'm talking about? It's the wheel arrangements of diesel/electric locomotives. As per the old steamers (Whyte Notation) and their arrangements of 2-6-4 or 4-8-4+4-8-4, more modern locomotives use a similar nomenclature known as the UIC classification.

The basic idea is that, per bogie, a letter starting from A is assigned, determined by the amount of wheelsets; where a wheelset is 2 wheels plus an axle. The letter is incremented from A for each wheelset. A bogie with two wheelsets will be defined as a Bo, 3 wheelsets means a Co.

You'll notice I put the letter 'o' after the B and C above. This is because, on some locomotives, the wheelsets can be mounted on the frame. The 'o' indicates that the wheelset is mounted on an attached bogie. I was about to write that I hadn't officially seen an 'Ao' yet; wouldn't the bogie spin on the wrong axis and derail? It turns out that it wont if you mount it correctly. The Japanese DD54 (wikipedia.jp) is of class Bo-1-Bo. I do note that it's not an 'Ao'... but it is indeed a bogie with only one axle!

As above, not all wheelsets are mounted on bogies, and not all wheelsets have power attached, so you'll need to read the wiki link on UIC classifications to really get the full picture.

Japanese wheel arrangements

My favourite Japanese electric, the EF-66 as seen below, is a Bo-Bo-Bo.

This majestic piece of equipment therefore has three bogies with two driven wheelsets each. The Japanese fashion is to have traction motors strapped onto each axle in parallel.

An now, the DE10

This is one of the more light-weight, shunting-type locomotives used around yards in Japan or for shorter freight movements. It's seen below at Aomori, ready to pull the passenger consist of the Nihonkai that I travelled on away from the EF81 that was ready for a snooze.

I recently acquired a Micro-Ace model of one in the Watarase Railway colours. Gold and Maroon is really quite fetching over the standard Red/Grey/White/Black.

Anyway, back to the point, I was reading the back and saw that the 'real world' technical specifications indicated that the wheel arrangement was infact AAA-B (where that B can be translated to a 'Bo'.) I was expecting Co-Bo... not AAA. What gives? It turns out that, for tractive effort and weight distribution, the front bogie is actually articulated! So they've classified it as three mini-bogies of one driven axle each.

I then recalled seeing mentionings of this on the JNS Forum posts here [DE10 - What does it haul?] and here [More tech questions re Class DD51 and DE10 diesels]. The latter links to a blog post titled 【仙貨へGO！】この足は誰のもの？仙貨に搬入されたDE１０の台車たち from a Japanese enthusiast by the name of 歩王(あるきんぐ) (Arukingu). 仙貨 (Sen-kamo) is actually an abbreviation of Sendai Kamotsu, the freight yard in Sendai. Do not get this confused with Sendai Transport, a comedic rock band! The title of the blog post loosely translates to: "[Let's go to Sendai Freight Yard] Who's wheels/legs are these? Lifting a DE10 Locomotive." Here's the main picture you really need to see:

1 Comment

8Jul/150

SqlDateTime vs DateTime (The battle of the Milliseconds)

This was a good one. I had stored a data row both locally in SQL CE 4.0 and then remotely via a WCF service to SQL Express 10.50.4000. I also then stored the 'most recent' date of the most recent local row in a local 'settings' table as an nvarchar. This was formatted as yyyy-MM-dd HH:ii:ss.fff. I'd then pull this date from the settings table and send it to the remote service that asked are there any records newer than this date?.

The remote service would usually repond with the correct answer, when there were newer rows. But, every so often, it would also respond with Yes! In fact there is! Here is the record with the date you just specified!. WTH? I sent the remote service the exact date and it responds with the same record, which is supposedly newer (no greater-than-or-equals here) when it is exactly the same? ... or is it?

It should not have returned this record. The date should have matched the check date I sent the service and the is there a record with a date greater than the check date should not have been true...

DateTime objects stored in MSSQL lose accuracy

Turns out that, in the land of the datetime data format in MSSQL, that the accuracy is not maintained.

MSSQL, with the datetime format, can only store milliseconds of ##0, ##3, ##7. There's a lot of posts on this splattered all over the web.

Be careful when storing a datetime as a string

So what was my issue? I was getting the datetime from my local record and storing this as a string in another table, called settings, which was a key-value-paired one-size-fits-all user-settings table.

I was formatting it to the correct SQL format, preserving the milliseconds. Of course, I could, in this case, store any 3-digit millisecond value I required.

When I then read that back as a datetime in C#, the value was rehydrated correctly.

When I then sent that to the server, the value was up to 2 milliseconds less/greater than the ACTUAL record in my local db and the remote db. Therefore the server would, every so often, return the record I had based my date off... because I was storing it as text more accurately than MSSQL was in the datetime format.

SqlDateTime to the rescue

C# has a data type known as SqlDateTime. If you grab your DateTime from any object, pipe it into the constructor of a new SqlDateTime and then grab the .Value on the other end, you'll wind up with the DateTime as it would be stored in the database!

Tada! You'll no longer have to worry about inaccurate milliseconds!

In fact, you should probably switch ALL DateTimes in your C# app to SqlDateTimes if you want to get rid of shitty little bugs that will only occur when you do something at an exact millisecond that CANNOT BE STORED IN MSSQL.

End Rant.

No Comments

2Jul/152

Power Mac 7200: PC Compatibility

The 7200 was marketed as PC Compatible out of the box and came stock with an 820-0728-A Apple PC Compatibility Card. Getting one of these to work without the original disks was quite a challenge! Let's start by checking it out...

Once in the case, there's ribbon cables and audio cables running everywhere.

The External Cable (is not required)

It turns out that if you boot the machine up without the cable patched in then it isn't needed; the PC display is routed internally through to your monitor.

I'm going to guess that the internal ribbon cable, as seen in the last picture above, is the reason for this. It must route the video output through to the standard Macintosh video. I don't know if this causes a performance hit.

Upgrading it

My initial understanding was that the CPU is fixed and so is the on-board 16mb of RAM, but there is an extra slot that you can slap up to 64mb into. See Oliver Schubert's notes here. I therefore purchased an additional 64mb on eBay to get my card to 80mb. Make sure it is 5v NON-EDO FPM 4x64!

The RAM arrived from eBay (new DIMM is above old in the picture above) and I plugged it in and turned it on. Windows still reported 30mb of RAM (2mb to video, I imagine) and so did the BIOS. I initially thought I'd bought a dud... after a few reboots and poweroffs I still couldn't get the total amount to register. I powered the machine down completely and inspected the card. It seems that the DIMM had around 0.5 of a millimetre more to be pushed into the slot!

Rebooting with a properly seated DIMM showed 64mb in the BIOS. I had actually expected 80mb if it was working properly, as the on-board 16mb should've totalled to that. Nothing I did further remedied this. 64mb worked for me though.

For fun, I removed the DIMM altogether and rebooted. Trying to start the PC got a loud beep. Nothing. It wouldn't start... I then read the actual manual:

Your PC Compatibility Card has one socket available for RAM (random access memory). Some versions of the card come with a DIMM (dual inline memory module) already installed. On these cards, you can increase memory by replacing the installed DIMM with a greater-capacity DIMM.

Some versions of the PC Compatibility Card do not come with an installed DIMM. On these cards, you must install a DIMM in the socket prior to installing the card in your computer. Otherwise, the card will not work.

Hah... so... my card had 32mb in there.. I removed it and added 64mb. When it was partially inserted it somehow appeared as 32mb. When correctly inserted the 64mb was visible.

I then checked out PC Setup and saw that, when no RAM was in, it told me NO RAM.

Duh...

Mac OS 8.1-8.6

The card just works. The PC Setup Control Panel is installed with the OS and command-return switches you to the PC. I hadn't tried networking from Windows... but I had found that it didn't seem to be configured.

As that the machine came with this OS and had Win95B installed on the PC side, I didn't have to go through anything to get it working. It wasn't until I installed 9.2.2 fresh that I was at the whim of 90's vintage technology.

Mac OS 9.2.2

Nothing. No control panel, no command-return. Mac OS 9 Cross-Platform Issues reports that you can get it to work under 9.0.4... and so I tried for myself on 9.2.2.

Note: This turns into a rant very quickly. If you just want the required files, then jump down to here.

Tips for Running Windows on Mac has a FAQ for getting it to work. They state that networking hadn't worked since 8.5 (probably why it didn't work when I tried.) Their link to PC Setup 2.1.7f failed me, but I found it over here at the PC Card FAQ. It is also available on alksoft's site labelled 'Stuff that might be useful'. Of course... that 'Mac Drivers' link didn't work... so grab it from the PC Card FAQ.

Did that work for you? It didn't for me... the zip from PC Card FAQ had a __MACOSX folder in it and a file that was unrecognised by my 9.2.2 installation. If it still works when you read this, go to the official site here and download the actual driver itself from them.

It worked! And then asked for registration details... enter the following:

Licensee Name: FREE
Site Number: 469
Authorization Key: UEV-EVZ-7TU

...and I then it tells me that I need PC Setup 1.6.4 installed first. Yey! You'll find the first file you need here. Extracting the BIN will give you a disk image. Simply double-click it and Disk Copy will mount it onto your desktop. Run the installer and reboot.

Once rebooted, I thought I'd try and muck around with PC Setup 1.6.4. It seemed to work, but I had no HDD. I had a 1gb disk in there that I wanted to use natively. Don't even bother trying to use real PC Partitions... go with a Drive Container on a spare disk/folder.

PC Setup will take years to build the drive file, so go make a coffee. Once it's done, start the PC. You'll need a boot disk. There seems to be one at the PC Card FAQ with CD-ROM drivers and the like.

Note: You must insert the floppy only once you are on the PC side. A floppy inserted on the Macintosh side will be mounted onto the desktop and be invisible to the PC. Switch to the PC using command-return and then insert the disk. Use command-E at any time to eject the disk.

Anyway, back to the floppy disk image... the files you've downloaded will prove problematic. It'll be next to impossible to create the disk images as the metadata from the zip files seem to be missing and the files wont be openable in Disk Copy or any such program. Your best bet from here is to load up another machine, say Linux or Windows, and create a floppy. Here's someone else who had the same trouble. Their answer was to get another person to write a physical floppy and mail it to them!

I tried this, booting up my old windows PC with floppy drive, but it didn't work! I'm thinking the zip format was the issue... so I started searching deeper. Googling for more information got me to Oliver Schubert's DOS Card FAQ which had pointers to Apple's download site. This was full of dead FTP links, but gave me the real file names in BIN and HQX. I slapped these into google and came across this directory listing. I don't know who you are yahozna, but I love you. The files were there!.. sitting, waiting to be downloaded. And shite, sometimes things just work: they extracted and mounted perfectly via Disk Copy! I took a copy of the second disk for safe-keeping also.

Turns out this disk isn't bootable. Go figure. You're actually meant to have installed DOS 6.22 from the disks that were originally included with the DOS Compatibility Card. I don't really want to do that, so we'll try trick it. We really just want the drivers for our Win98 install.

Grab the Windows98_SE boot image from here and burn it to a floppy. Once created, grab CDROM.SYS from the PC_Compatibility_1.6.4-2of2 and copy it onto the Windows 98 disk. Either delete an existing driver (like BTCDROM.SYS) and rename it to that, or edit CONFIG.SYS and add in a line for CDROM.SYS.

Or, you can just download the boot disk here that I created which will work fine! It also has all the required networking files.

Boot this floppy and crawl to a DOS Prompt. You'll get a warning that C:\ is no good, as expected when no partitions exist. Run FDISK and create a new logical partition. Reboot, booting off the floppy again and we should be set... you should now have a CD-ROM drive and usable C: Drive.

Usually from here, you'd run setup off the CD. Fortunately, we know in advance that the CD will be inaccessible on the second reboot into Windows setup. So, format your disk here and then copy the win98 folder to C:\. You can then run SETUP.EXE from C:\WIN98SE\. This will save a lot of headaches!

That last screen... Windows will sit there 'updating settings' for a very long time! Prepare to wait for around 30 minutes.

Now you're at the desktop, slap the PC_Compatibility_1.6.4-2of2 disk back in and run setup.exe. Keep all the boxes checked, install the drivers and hit restart.

After a reboot you should then have your CD-ROM drive in My Computer! Command-Click on My Computer and then choose properties. Go to the Devices tab and you'll see three items that need drivers. With the Windows 98 SE CD in there, you can choose properties and then Reinstall Driver. Let Windows choose the driver off the CD and you'll be set.

At this point, audio still didn't work. Looking at all of the manuals for the cards, you'll note that they all output audio through the CD Audio cable. It's actually patched in... instead of the audio from the CD drive going straight to the motherboard, it is fed into the cd audio input on the PC card, mixed (I assume) and then another cd audio cable connects the cd audio output of the pc card to the motherboard.

The big hint here was that, after installing Mac OS 9.2.2, had I correctly set up the Mac for CD Audio input? Switching back to the Mac and checking the sound panel, I noticed that I was mute to the world. There was no input specified! An easy fix: set this to CD Audio and switch back to Windows. Tada! All the nasty sounds of Windows 98 SE. Actually... I never did mind that guitar solo on the Welcome screen.

Networking wasn't too difficult. Following the 'How do I network the Mac and PC side at the same time?' instructions at the bottom of the pc card faq, I downloaded the DOS NetWare Client file from FreeDOS, copied it to a CD and then transferred it over to Windows on the Mac.

Note: You cannot use multi-session 'USB Style' CDs in the Macintosh. If you're copying files onto a CD in Windows and want it to work in the Macintosh then you have to do it the old way. Select 'With a CD/DVD Player' rather than 'Like a USB Flash Drive'.

Anyway, back to the networking... There's no need to do much here, I've put all that is required on the floppy image I've created. Slap it in and drag the NWCLIENT folder to C:\.

Edit AUTOEXEC.BAT and make sure the following lines are at the end of the file, in the following order:

C:\NWCLIENT\LSL
C:\APPLE\MACODI

I'm assuming you would've done all of this from a Command Prompt window inside Windows 98. So reboot your machine once this is done. Hit ESC when you see the pretty Windows 98 loading screen to see what DOS is doing underneath.

Once back in Windows, go to control panel, networks and then add a new adapter. Select the ODI adapter under the 'detected' category. It'll take a really long time... and won't really tell you that it's doing anything... but it is busy! Just leave Windows at the desktop at this point. It shouldn't ask you for a Novell Disk at this point; if it does, then you need to restart the windows side and check your errors on boot up.

Once installed, reboot as Windows asks. When Windows loads, you should be prompted with a login for Client for Microsoft Networks. You can just hit enter here to set your password as blank.

Once booted, I got to Windows, jumped into a command prompt and typed in IPCONFIG. Oh goody! I had a 169 'internal' IP. This wasn't going to work. There had been no errors, everything seemed to be fine... but PC Setup 1.6.4 on Mac OS 9.2.2 wouldn't let my packets flow. Trying a renew_all on ipconfig reported that my DHCP server wasn't available.

I thought I'd try the patch that was meant for Mac OS 8.5, but that didn't work... it installed, I got my newly patched extension, but on a reboot I still couldn't contact the outside world. Based on the post from Phil Beezley on the FAQ from Oliver Schubert:

...On some Macs, it is also necessary to replace the extension called Apple Enet with the Ethernet (Built-In) extension provided with Mac OS 8.5.
The more official solution to the network problems when using Mac OS 8.5 onwards is to use PC Setup 2.x.

Prior to trying 2.1.7f, I thought I'd try replace this extension. I inserted the Mac OS 8.5 CD, located Ethernet (Built-In) and copied it into the System Folder. It complained that there was an older version in there... how does that happen in 9.2.2? Anyway, You then need to delete/disable/move Apple Enet. Reboot the Macintosh.

It came back up... no errors. Chooser still worked, so did browsing the internet on the Macintosh side... so... I booted into Windows. Command Prompt reported a perfectly defined IP address from DHCP. Internet Explorer even tried to render a page!

After rebooting, I was on the internet! Windows 98 SE is working beautifully! I quickly tried MOD4WIN... nostalgic much? I do wish I could find a copy of Vibe, the MP3 Player that turned into Sonique.

For those who didn't read the fine print

Here are all the files mentioned and how to use them.

Files	Comments
Apple Macintosh PC Setup 1.6.4 Disks PC_Compatibility_1.6.4-1of2.img.bin PC_Compatibility_1.6.4-2of2.img.bin	The first disk contains the Macintosh side and will get 1.6.4 installed on any Mac OS up to 9.2.2. The second disk contains the PC drivers. This is NOT a boot disk. The original expectation is that you have already installed MS-DOS!
Macintosh PC Setup 2.1.7f pcSetup217Mac_22Aug2000.sea.bin Windows Drivers for PC Setup 2.1.7f pcsetup217.exe PC Setup 2.1.7f Setup/Installation Manual 217finalpcsetupinstall.pdf	These files were all secured from the Wayback machine. I have no idea if they work or not!
My Windows 98 SE Boot Disk BOOT98SE.img.sit.hqx	This disk is bootable and contains the CD driver. It is originally the 98 SE Boot Disk. So it'll drop you to a command prompt where you can use FDISK, FORMAT.COM and then run SETUP from the CD. I actually recommend that you copy the WIN98 folder to your C drive first! (call it WIN98SE) and run SETUP.EXE from there... that way you wont have to practice magic when it can't find the CD drive during installation. This also contains the Network Drivers. Copy the NWCLIENT folder to C:\ and edit AUTOEXEC.BAT as specified above.
50mb Hard Disk Image of above boot disk TinyBootDisk.sit	As mentioned, this is a bootable harddisk image that should work for people having issues booting from floppy disks. It contains everything you need for CD and network. The Win98SE Boot Disk RAM DRIVE is also loaded as D:\ (CD as E:\)
PC Compatibility Card Manuals 7" Card Manual12" Card Manual	The original Macintosh manuals for each card.

It's been a pleasure...

2 Comments

1Jul/157

Power Mac 7200: OS 9.2.2

Mac OS 9.1 is officially the final OS supported on the Power Mac 7200. I've got a new PCI graphics card and PCI USB card on the way and so I'll need Mac OS 9.2.2 for full compatibility. Below details how to achieve this.

Mac OS 9 Lives

I had previously downloaded 9.2.2 from here. It's known as Mac OS 9 Lives and it comes as an ISO with Apple Software Restore and a disk image of a partition with 9.2.2 fully installed. To install the software you only need to run the restore and it'll turn a partition on your local machine into a bootable system image.

..of course, I installed this and rebooted and got the standard This startup disk will not work on this Macintosh. I assume from here you could hack the system folder and edit the gestalt ID matching code (as was done with the 68k) but I instead chose to use OS9 Helper.

To get my machine booting again, I had to find a boot disk that worked fine on my hardware to switch back to the 9.1 startup disk. My old Presto PPC boot disk wouldn't work on this PowerPC... so I had to guess how to boot from a CD. Turns out, with the 9.2.2 boot/firmware, that holding down C at boot will startup from the CD.

Official 9.2.2 ISOs

If you want the real ISO, then go there's more information on it at Macintosh Garden: Mac OS 9.2.2 Universal. You can also get it at winworldpc.

This wasn't going to work either, so I started researching and heard out about...

OS9 Helper

There's quite a few links that explain how the Power Mac 7200 owner should use OS9 Helper to hack OS 9.2.2 into submission. The basic idea is to download OS9 Helper and run it on your machine.

This application will not hack/fix an installed version of OS 9.2.2. Instead, it requires that a version of 9.1 or a patched version of 9.2.1 reside on a local hard disk. It will then update this to the version you require.

This stopped me from using the partition I'd just created with Mac OS 9 Lives and therefore made me use my previous 9.1 startup disk.

The app requires that the relevant Apple OS Update for the version you wish to install be downloaded locally. I didn't try the download links available... instead I searched the net. Finding this was much easier than expected; it turns out that my own ISP still has a cache of Macintosh software! iinet's public FTP located here has a whole swathe of archaic Apple software to download!

Once you've got the required updater, re-run OS9 Helper. I quickly found out that you can't just jump to 9.2.2, you'll need to follow the upgrade steps and install 9.2.1 first. Installing 9.2.1 via OS9 Helper is a breeze. Once done, restart your Mac. It should boot back up to your desktop without issue.

Once booted, set up 9.2.1. You're now ready to apply the 9.2.2 update. Do this via OS9 Helper once again.

And now you're done!

7 Comments

25Jun/157

Power Mac 7200: Power Supply

Whilst searching for a CRT on eBay for the Quadra (that's another story), I came across this item. It was listed as being PC Compatible and, after my last efforts of trying to get a DOS Card to work, I decided to tackle this one.

The Power Mac 7200 was marketed as a PC Compatible because it came with a PCI card containing all the required hardware to run a PC. This card includes a 100 MHz Pentium processor that can have a maximum of 64 MB of RAM dedicated to the DOS/Windows operating system.

Powering it on

The case contents rattled a little, so I opened up (there are two push-buttons on the front under the lip) and inspected it. A few plastic lugs had snapped loose, but there was nothing conductive. With the case open I jammed in a power cable and hit the power button.

Nothing. Not even a zap, whirrr or beep. Just silence. I hate that...

Basic principles told me to disconnect all unnecessary components and try again. No love... Pulled the CMOS Battery, held the CUDA button (but not for 15s), left power off 10minutes... no go.

Testing the power supply (Delta DPS-150GB A) (Apple 614-0039)

From here I thought I'd tackle the power supply first. I didn't want to believe it was the logic board. I disconnected the cables and removed it from the case.

There are 4 screws holding the lid of the power supply on. After removing these, you'll then have to slide the lid along the main trunk of power cables. Pushing the cables into the supply will make this easier. The fan has a 2-wire cable which easily pops off the main power supply circuit board.

Once open, I first inspected all components for damage... all looked good. Testing the fuse showed that it worked fine... conducting power. I then grabbed the multimeter and tested all of the pins. I found 5v on pin 4, but no voltage anywhere else.

Here's the pinout for the main 22-pin connector, looking at the plug as if it was facing away from you. Pin 1 is top-left, pin 22 bottom-right.

+5v	+5v	+5v	+5v	GND	GND	GND	GND	GND	N/A	-12v
TRKL	+5v	+5v	+5v	+5v	GND	GND	GND	GND	/PFW	+12v

And then the secondary 10-pin connector. Pin 1 is top-left, pin 10 bottom-right.

GND	GND	GND	GND	-S
+12v	+12v	+12v	+12v	+S

These power supplies are triggered by the power switch on the motherboard. Plugging them into the wall will get them in to 'stand-by' mode and power should be visible on certain pins. To test this, plug the power supply into the wall and check the following:

(22-pin connector) +5v is visible on pin 12 (Yellow)

One important point is that, in my case, the 5v above showed up on the correct pin. The power supply still would not power up. It turns out that the above test is not fool-proof; it'll simply tell you if the initial 'trickle' power is available.

To get this thing to power on whilst disconnected from the motherboard, follow these steps (Thanks goes to LT.Maddog420 on the Tech Guy forums):

On the 10-pin secondary cable, connect pin 5 (White) to any of pins 1-4 (Black)
Still on the 10-pin secondary cable, connect pin 10 (Brown) to any of pins 6-9 (Orange)
Confirm the power supply is plugged in to the wall and that the pins connected above are not exposed or touching metallic surfaces.
Now, on the main 22-pin power plug, connect pin 12 (Yellow) to pin 21 (Purple)

The above should jump-start the power supply. The fan should at least fire up. If you get nothing then you've got a dead power supply. This would be the first item to replace in a Macintosh that doesn't power on. Of course, when the supply died it could've also fried other parts... but replace the power supply first as it's cheaper. I tried to jump-start mine and it didn't work at all. I decided to pull it completely apart for thorough inspection.

Cracked Circuit Board

Once out of the casing, the issue became quite obvious. The base circuit board for the power supply had a crack in it. The crack formed a semi-circle around the area where the circuit board is held by notches in the metal case. It seems that, somehow, the board has received lateral pressure and cracked! It doesn't quite make sense as the board is thoroughly enclosed. I can only imagine that weather/heat has caused this. I have a hunch that this machine had been out in the elements for a while.

There also seemed to be new flux and solder at the base of a 3-pin component. I really wouldn't be surprised if this had been repaired in its past life; this machine is nearly 20 years old.

Repairing the crack was pretty straight-forward. I was really lucky that this was a single-sided circuit board with large tracks. If there had been tracks on the top side, then this would've been a lot more difficult.

I bared the copper on the tracks around the solder joints and messily bridged all of the component pins. I made sure that I followed the tracks and didn't bridge any circuits. My butane-powered soldering iron decided to let its tip melt in the process and so the first fix shown below looks really crappy. I bought a proper soldering station (I needed it to work on the DOS Card for the Quadra 950) and re-did the soldering. Hence the two pictures of the finished job below.

And then... the friggen thing spun up! Using the jump-start instructions above, I bridged the two wires and then joined yellow to purple. It felt like I was hot-wiring a car and I, honestly, had very little faith in my hack working. I had a celebratory beer as the fan kicked off and I then crossed my fingers that the logic board wasn't also damaged.

A final note: be careful when pulling/pushing the bunch of wires in and out of the power supply case. You can easily peel the insulation off the individual wires and the last thing you would want is a short!

7 Comments

24Jun/153

Quadra 950: DOS Cards

I remember back in high school that we had DOS Cards in the Macintoshes we used for Multimedia class. We were either programming Hypercard Stacks or switching to the DOS environment and fragging eachother in Doom II. We weren't meant to be doing the latter... but it was hard to resist.

I had always been impressed that the DOS side worked just as well as the Mac side and switching was seamless. It all makes sense now why the DOS side kept running when switching and why it all ran so well; the DOS card created a whole PC running independently of the host Macintosh.

To re-live all this, I wanted to find a DOS Card for the Quadra 950. Researching the cards lead me to believe that the majority would fit into the the PDS Slot, but I wanted to keep my PPC upgrade in there. I therefore began the hunt to find a Nubus DOS Card.

Some light reading...

First attempt at acquiring one

I happened across an Orange Micro PC Coprocessor Card (dated prior to the OrangePC 290) with a Cyrix 5x86 on eBay. Bidding started at USD50. I bid up to USD70. I was in the lead until the last second when the price nearly doubled to USD126. Sounds like I'm an eBay newbie but, on the contrary, I just wasn't expecting the price to go that high. I actually wonder what the final bidder put down as a max bid... only the bidder ever knows with eBay, the seller only ever gets to see the final auction price and any bids below that.

This kind of crappy bidding brings up a good point: I like how Yahoo Auctions Japan actually extends the auction in the last five minutes, for five minutes, if someone places a bid. That way, just like in a real auction, the final bidder with the most money actually wins; rather than the one with the lowest latency.

The conclusion? These things are in demand!... This model happened to be a Cyrix 5x86 SL50 and was a little below-spec anyway, so I was happy to sit tight for something gutsier.

Orange Micro: OrangePC 290

eBay alerts are all well-and-good when the sellers list their items correctly. Unfortunately, this item was listed as shipping to the US only. I usually don't bother begging, as you usually get a flat-out "no" in response, but I asked the seller if they'd ship to Australia. As luck would have it, they did... but it was through the global shipping program. Not to be discouraged, I took the gamble and bid anyway... I won!

It seems that this card was worth over USD$2500 back in the day. See The Original Macintosh DOS Compatibility Card (Houdini I) for a price list... way down the document. I haven't checked the rest of the doc for valid information on my scenario (I don't have a Houdini card), but I'll read it at a later date when I have Win95B+Plus! running on my Quadra.

This card is came equipped with a genuine Intel 486 DX4-100 CPU and 32mb of RAM. I scoured the internet and found the drivers on the Wayback Machine. Product information is here and Downloads and drivers for the OrangePC 290 are here. Installation seemed overly-easy. Running the application gave a very simple configuration interface. Thanks to all my partitions I could easily allocate the space on one to a virtual HDD file. It seems that you need to use real floppy disks instead of images... Use Disk Copy to create those via the "Make Floppy Disk..." menu item.

The first warning, as below, was that my Video mode was unsupported. As you can see, it was configured for internal video, but the desktop mode didn't seem to gel with the OrangePC card. I tried quite a few resolutions (not really trusting my MAC to VGA video converter) but couldn't get it to agree with any mode. I was beginning to wonder if this was actually a hardware issue with the card itself.

I then hit Cold Boot on the setup panel and ... nothing ... 10 seconds later an error: The OrangePC card is not responding to the Macintosh and the error code 32. I couldn't find anything on that error number, but googling the text gave the standard advice of (taken from Orange Micro's FAQ page):

Q: When I launch OrangePC, I get an Error message saying ``The OrangePC is not Responding."
Remove the OrangePC from the Macintosh. With a pencil eraser, clean the PCI contacts. Do the same for the Memory (DIMM or SIMM) modules. Reseat the memory modules on the OrangePC, and insert the OrangePC into the Macintosh. If possible, place the OrangePC card in the slot closest to the Macintosh processor.

I decided to go down the cleaning route and removed the RAM SIMM. Everything then started to become very clear... the teeth in the socket were loose. I don't even know if that's the right term, but either way the three left-most contacts were going to be making very dodgy connections... no good for low-level digital logic. I jumped straight on eBay and found a local 72-pin SIMM socket and ordered it... it's 90-degrees instead of the 22.5 angle, but it'll be a good test.

In the meantime, I removed the SIMM, put the card back in the Macintosh and tried again... this time OrangePC told me that the Memory configuration was incorrect. Slightly interesting... it can tell that the chip isn't there (there must be a latch driven when the chip is in, must be on other pins.) I unseated the CPU and checked for further damage, but it looked ok... I then inspected the rest of the board. There are dints and scratches all over it, but none look track-threatening. I reseated the SIMM as best as possible with its loose teeth and tried again.

Finally, prior to any actual surgery, I grabbed a hair-drier and gave it a once-over. The age-old trick of reheating dry solder joints is a good one. I've never tried it, but I could see dry joints all over the place. A hot hair-drier will actually slightly melt the joints and, as long as you don't angle the board, hopefully re-join any damaged connections. It's a crap-shoot, but it was worth a try. Unfortunately it didn't improve the situation.

Googling further, I came across Andrew's OrangePC 290 page. This guy is a legend; That is all. The site might as well be the technical manual for the card. So lucky to find it. It documents the jumper settings... I assume these would come set out of the factory, but they are there to be configured. It turns out that he has all the information I need for the CPU I have installed. I reviewed the jumpers, and found that they were all wrong. They didn't match the CPU installed at all. I reconfigured the jumpers as per Andrew's page... but the board still would not function.

Re-inserting it and starting OrangePC threw an error Type 1 at me... hadn't seen that before. Oh, the joys of playing with vintage hardware! Type 1 errors are address errors... I assume it's having issues finding the hardware. A reboot didn't help. I powered the machine down and was about to put the card in another slot when I realised I'd bent a pin on the Nubus connector. No wonder the software couldn't find the hardware.

Don't do anything with vintage hardware in a rush... Straightening the bent nubus connector pin proved relatively easy. I inserted it again, gently, and power up the machine. No love... errors... I think we'll see if the RAM socket repair will work.

One note, I attempted to set the video mode to external via jumpers 11 and 12. Andrew's site indicates that there are two configurations, but I tried all. The software actually registered that external mode was selected... it even stopped me from opening the internal view of the dos environment. That only confused me further... the Macintosh could talk to the card fine... it just seems that when it throws the final boot command that the card does not respond... maybe it is the RAM/CPU combo. I really don't know what the history of this card is... for all I know it's been out in someone's flowerpot catching rays for the last 20 years.

Further attempts to get this working resulted in very hot CPUs and other ICs on the board, random bus errors on boot of MacOS and system crashes left, right and center. Not much fun... this card is about to get written off as a dud. I tried reverting to 8.1, switching off the PPC card, switching back to the stock crystal. Nothing. It just wouldn't boot.

I had a lightbulb moment: I could re-wire the first loose tooth on the ram socket prior to receiving a whole new socket. I found some winding wire from my toolbox and installed it. Nothing... it still failed with the same errors... made me believe that the card was hopeless.

...this effort proved fruitless. No change in error messages.

In the never-ending quest to fix this thing, I also replaced the CPU with a valid substitute. I bought an AMD DX4-100 from a seller on eBay and gave it a go... no love.

The RAM socket arrived... I replaced the socket, but that didn't work either.

Could it be the RAM SIMM? I've another arriving sometime in the next week... will give it a go.
Otherwise... I'm beginning to think that this is a dead-loss. Time to sit back and wait for another one to appear on eBay.

3 Comments

« Newer Entries Older Entries »

Random Photos

DSC00323

Aizu-Wakamatsu - July 2017
Photo Album Index

modelrail.otenko Trains, computers, vintage, retro, model railways… the lot…

Rail-set Train

Ajikawaguchi

Timetables

Timetables

Timetables

Japanese wheel arrangements

An now, the DE10

DateTime objects stored in MSSQL lose accuracy

Be careful when storing a datetime as a string

SqlDateTime to the rescue

The External Cable (is not required)

Upgrading it

Mac OS 8.1-8.6

Mac OS 9.2.2

For those who didn't read the fine print

Mac OS 9 Lives

Official 9.2.2 ISOs

OS9 Helper

Powering it on

Testing the power supply (Delta DPS-150GB A) (Apple 614-0039)

Cracked Circuit Board

First attempt at acquiring one

Orange Micro: OrangePC 290

Random Photos

Search

Tags

Ads

Archive

Meta