Using files from the same architecture solved the problem for me. One way of preventing this sort of thing would be to add a little footnote to the installation guide, in section 4.3.2.2 [1], just after footnote 8, that the iso image should be for the same architecture as the hd-media files.
The reason I ended up with two different architectures in the first place was due to the way I clicked through the www.debian.org site, trying to find out how to install the most recent testing distribution using a USB stick (where I needed the 'flexible way' of creating a USB stick because the capacity of my USB stick was only 128 MB, preventing me to use the more convenient boot.img). Apparently the link to the installation guide automatically brought me to the i386 version of the manual, whereas I should have needed the amd64 manual. [1] http://d-i.alioth.debian.org/manual/en.i386/ch04s03.html#usb-copy-flexible -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100917165059.gd1...@pinnau
