Amiga Bootblock Reader v3.00

[jasonver2.0]

Hello fellow Amigans

I have released a new version of my program

It uses .NET 4.0 and is Microsoft Windows program to scan ADF and Bootblock files on PC

- Recognises 1716 Bootblocks
- Newly redesigned interface (mostly)
- Lots of little changes all over the place
- Includes boot pictures for many of the recognised bootblocks
- Can now use WinUAE / FS-UAE from any location (WinFellow doesn't have command line arguments and so cant be used to test bootblocks)
- Program uses PNGs generated by WinUAE screenshot function (You can create your own if needed)

I'm not sure if anyone is interested in having a program like this anymore. I will stop working on this if there is little to no interest

Known problems:

- If you add a String search that the program doesn't like it will refuse to scan correctly afterwards. Your string search contains a character that causes the scan routine to break, you will need to edit the search.brainfile file in a text editor and remove the offending line. (No blank lines)

- While i have endeavoured to make the scanning as accurate as i can, in some cases there will be some inaccurate detection.

Box.net archive containing program and boot pictures
https://app.box.com/s/iq9wwc68sjifjf5724ezvdc603iocfwx

ABR without boot pictures to allow attaching in forum
ABR1.30.zip

Bootblock archive
Bootblocks.zip

5/03/19: Fixed Amiga emulator setting defaulting to WinUAE
6/03/19: It seems i broke .ZIP handling (containing ADF's) - fixed
13/03/19: When ABR found a ADF file, the 'Boot Disk' button wasn't enabling for some reason

[Phantasm]

Might want to mention that this is a PC application not an Amiga application

[Crashdisk]

Hello Jason,
it's good to see you back here!
I just tested the new version of your program and I have a bug at launch:

System.IO.FileNotFoundException: C:\Program Files(x86)\WinUAE
   à System.Diagnostics.FileVersionInfo.GetVersionInfo(String fileName)
   à AmigaBBReader.frmMain.GetFileVersionInfo(String filename)
   à AmigaBBReader.frmMain.frmMain_Load(Object sender, EventArgs e)
   à System.EventHandler.Invoke(Object sender, EventArgs e)
   à System.Windows.Forms.Form.OnLoad(EventArgs e)
   à System.Windows.Forms.Form.OnCreateControl()
   à System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
   à System.Windows.Forms.Control.CreateControl()
   à System.Windows.Forms.Control.WmShowWindow(Message& m)
   à System.Windows.Forms.Control.WndProc(Message& m)
   à System.Windows.Forms.Form.WmShowWindow(Message& m)
   à System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

The path is wrong "C:\Program Files(x86)\WinUAE" because it should be "C:\Program Files (x86)\WinUAE"

Another anomaly, in the interface, it refers to 10 types of bootblock but your database contains 12 types of bootblock:

Boot Demo       > i
Boot Game       > g
Boot Loader     > bl
Boot Logo       > l
Boot Menu       > m
Copy Protection > p
Scroller        > sc
Standard        > s
Utility         > u
Virus           > v
--------------------
Crack?		> cr
Copier?         > cm

Thank you for your tools, it will help us to improve our database . I've been working on bootblocks for a few months now

[DamienD]

Originally Posted by Crashdisk

The path is wrong "C:\Program Files(x86)\WinUAE" because it should be "C:\Program Files (x86)\WinUAE"

...but not everyone "installs" WinUAE.

For me my path is as follows: "C:\WinUAE\WinUAE.exe".

Can we not specify where the WinUAE executable is via the program?

[Crashdisk]

Originally Posted by DamienD

...but not everyone "installs" WinUAE.

For me my path is as follows: "C:\WinUAE\WinUAE.exe".

Can we not specify where the WinUAE executable is via the program?

You're right, but on 64-bit systems, the official path is "C:\Program Files (x86)\WinUAE" for 32-bits installer and "C:\Program Files\WinUAE" with 64-bits installer.
The ABR error is related to a hardcoded path but customizable, at least in theory because the parameters are not saved

Optimized PNG in the zone (12.5mo to 6.35mo)

[jasonver2.0]

Sorry about the WinUAE thing, i removed all hardcoded references to WinUAE as the program can use any version of WinUAE or FS-UAE to test bootblocks. I forgot that i set the path on my copy it 'hard-coded' it at least to begin with.

I fixed the brainfile and removed the extra classes. I was testing out some new ones but forgot to revert the brainfile afterward

Ive updated the ABR1.30.zip in the first post

[jasonver2.0]

I will upload a archive of my bootblocks for anyone who wants it - someone can upload it to FTP if they want. I don't have a high enough post count recently to create a upload account.

[RoC]

Thanks for this update!

I have been using the previous one to test several BB.

[jasonver2.0]

Updated ABR again as it appears .ZIP handling was broken by excessive tinkering

[jasonver2.0]

Updated again due to accidently breaking ADF booting

[HOL2001]

For me there are no boot pictures in the
"Box.net archive containing program and boot pictures"

[RoC]

Originally Posted by jasonver2.0

Updated again due to accidently breaking ADF booting

Just downloaded. Thanks again.

[jasonver2.0]

Boot pictures are back in box.net archive. Sorry about that HOL2001

[HOL2001]

Many thanks!

[Crashdisk]

Repack : Full optimized pictures in The Zone

[HOL2001]

Nice! Many thanks!

[tmb]

just wanted to say, that programm is cool and i love the feature of scanning a whole directory with files for the bootblocks at once. great!

[breech]

Nice. I thought this was dead because the other threads were not being updated. Thanks!

[BarryB]

Definitely a worthwhile utility, as long as it genuinely recognises those bootblocks that are harmful/virus!

One issue, if I navigate to a directory from the Bootblock Display Tab and open an ADF, it doesn't seem to remember the directory if you open another file, it always goes back to c:\ so you have to navigate back to whatever folder you wanted! You can set a default ADF Drawer to a particular folder and use that all the time, it's kind of a pain as it seems you have to keep re-setting the default folder if you want to work in another folder!

[ma693541]

The 16 Bit Crew Bootblock virus is missing, maybe others too. Ran the program against an .ADF folder and there was a lot of "Unknown Bootblock" messages, virus or not, that's the big question.