General Category > LisaList2
Is there any way to use a BLU disk image of a Widget drive with an emulator?
drybones99:
I recently asked this question at 68kmla.org, but I was told to come here. I was recently able to transfer, using BLU (Basic Lisa Utility), a raw disk image of the Widget hard drive in my Lisa 2/10. However, I have been unable to get this disk image to be bootable in either LisaEm or IDLE. It is at this point that I turn to this forum for any suggestions on how I could possibly get this raw disk image to work in any Lisa emulator.
More information about my attempts can be found here in this thread:
https://68kmla.org/forums/index.php?/topic/59047-is-there-any-way-to-use-a-blu-widget-disk-image-with-an-emulator/
rayarachelian:
Hi, and welcome!
I've downloaded the widget BLU image from the 68kmla thread, and will take a look at the conversion output. BLU has its own format, which isn't the same as raw, but close.
Currently the two candidates are that I suspect, is it either has to do with interleave or perhaps the widget boot loader is different than the profile one. It's also possible that there's some horrible bug in the blu-to-dc42 tool.
rayarachelian:
So at first glance the conversion failed, there's not supposed to be this many MDDF's (this is like the superblock).
Pls do me a favor and upload the BLU file and not the dc42 either here if it will let you, or over on 68kmla.
thanks.
--- Code: ---
File size: 10350676
Filename: 3_-_BUILT-IN_PARALLEL_PORT_(10_MB_Widget_Hard_Disk).dc42
Sectors: 19456
Tag size each: 20
Sec size each: 512
Sector bytes: 9961472
Tag bytes: 389120
Image Type: 0 (0=twig, 1=sony400k, 2=sony800k)
Tagstart @ 9961556
Sectorstart @ 84
Maxtrack: 0
Maxsec/track: 0
Max heads: 0
Calc DataChks: db0b5b93
Img DataChks: db0b5b93
Calc TagChks: 1406b0aa
Calc TagChk0: 17bd45c2
Img TagChks: 1406b0aa
Sorting tags
Found allocation bitmap block at sector #0027(39)
Found allocation bitmap block at sector #0028(40)
Found allocation bitmap block at sector #0029(41)
MDDF (Superblock) found at sector #0026( 38) fsversion:11
MDDF (Superblock) found at sector #0134( 308) fsversion:11
MDDF (Superblock) found at sector #258a(9610) fsversion:00
MDDF (Superblock) found at sector #258b(9611) fsversion:ffff
MDDF (Superblock) found at sector #258c(9612) fsversion:ffaa
MDDF (Superblock) found at sector #258d(9613) fsversion:ffff
MDDF (Superblock) found at sector #258e(9614) fsversion:ffff
MDDF (Superblock) found at sector #258f(9615) fsversion:9009
MDDF (Superblock) found at sector #2590(9616) fsversion:9009
MDDF (Superblock) found at sector #2591(9617) fsversion:4d4c
MDDF (Superblock) found at sector #2932(10546) fsversion:3900
MDDF (Superblock) found at sector #2933(10547) fsversion:ff3d
MDDF (Superblock) found at sector #2934(10548) fsversion:ffff
MDDF (Superblock) found at sector #2935(10549) fsversion:f3f
MDDF (Superblock) found at sector #2936(10550) fsversion:2002
MDDF (Superblock) found at sector #2937(10551) fsversion:ffff
MDDF (Superblock) found at sector #2938(10552) fsversion:ffff
MDDF (Superblock) found at sector #2939(10553) fsversion:fff0
MDDF (Superblock) found at sector #293a(10554) fsversion:7273
MDDF (Superblock) found at sector #293b(10555) fsversion:fffe
MDDF (Superblock) found at sector #293c(10556) fsversion:4d50
MDDF (Superblock) found at sector #293d(10557) fsversion:fff8
MDDF (Superblock) found at sector #293e(10558) fsversion:08
MDDF (Superblock) found at sector #293f(10559) fsversion:fff8
MDDF (Superblock) found at sector #2940(10560) fsversion:fff0
--- End code ---
drybones99:
I have been unable to attach the file here, getting a "413 Request Entity Too Large" error, despite the file size being well under 16,384 KB, the stated maximum, at 10,109 KB, but my latest post in the thread at 68kmla.org has the original BLU file attached, unmodified from when it was originally created by BLU. It is not in the .dc42 format.
rayarachelian:
Good news, I found some bugs in the code, it's now producing an image where the tags are correct, however, bad news, attempting to boot from it throws a 10726 error.
I found a couple of bugs in the converter program, and now, looking with lisafsh-tool, I see that the blocks that have the boot loader on the profile match the converted widget drive. I then tried to repair the Widget image using the LOS install disk #1 and it failed to do so with error 200/663, but not sure what that means.
Also tried to boot off a good profile image and attach the converted image on a dual port parallel slot (you can do that by changing the preferences, telling LOS there's a 2 port card in one of the slots, and that, say, the upper port is a profile) but the disk isn't recognized.
So likely there's some more stuff needed to get this working.
Navigation
[0] Message Index
[#] Next page
Go to full version