exe-file-in-df0 does not work with assembly winner

thomas · 10 August 2010, 13:37

Download demo from http://www.scene.org/file.php?file=%...n.lha&fileinfo
unpack it to Windows directory, insert exe into WinUAE's DF0 -> does not boot.

Examining the "disk" from Workbench reveals that it contains all zereos, no file, no bootblock, no data.

It works well with other exe files, for example the Assign command from the Workbench disk. DF0 then contains a bootblock, s/startup-sequence and runme.exe as expected.

TCD · 10 August 2010, 13:43

Had the same 'problem' with other (demo) exe files that are bigger than the standard 880k disk. Guess it works as intended.

thomas · 10 August 2010, 13:55

Quote:

Originally Posted by TheCyberDruid

bigger than the standard 880k disk.

Oops. I didn't look at the size. It's more than 3 MB, this wouldn't even fit on a HD disk.

Perhaps WinUAE should throw an error message. Something like "this file is too big to be used as a floppy disk".

TCD · 10 August 2010, 13:58

Quote:

Originally Posted by thomas

Perhaps WinUAE should throw an error message. Something like "this file is too big to be used as a floppy disk".

Second that

Toni Wilen · 10 August 2010, 15:14

It is bonus feature that works and nothing more is needed. (next feature request would be: somehow detect if setpatch is needed and so on, it would never end..)

thomas · 10 August 2010, 15:25

What about the "this Kickstart needs 68020 or better" message? Isn't this bonus feature, too? "This file is too big for a floppy drive" is very similar IMHO.

Toni Wilen · 10 August 2010, 15:29

Quote:

Originally Posted by thomas

What about the "this Kickstart needs 68020 or better" message? Isn't this bonus feature, too? "This file is too big for a floppy drive" is very similar IMHO.

It is different. You can easily see if file is too large but not KS requirements just by looking at (possible mangled) file name..

Not good enough reason.

Toni Wilen · 10 August 2010, 15:57

Important question is: When should it complain about too big exe? If it does not fit in 880k image? But what if selected KS does support HD disk? Should it automatically switch to HD floppy mode (including possible unexpected side-effects) and only complain if it does not fit in HD disk?

"Image is too big" isn't the only problem.

thomas · 10 August 2010, 16:19

Quote:

Important question is: When should it complain about too big exe?

It should complain in the same case when you create that 880k-filled-with-zeroes ADF in memory. Seems like there is some kind of checking already, it just does not make it to the user.

Quote:

But what if selected KS does support HD disk? Should it automatically switch to HD floppy mode (including possible unexpected side-effects) and only complain if it does not fit in HD disk?

Would be nice if it could be that intelligent, but feedback to the user is more important than to improve the existing file handling IMHO.

Toni Wilen · 14 August 2010, 09:59

I checked the code and problem is simple: code that "inserts" the disk must not open any GUI dialogs (It is used for all kinds of disk insert tasks, for example configuration file disk inserts)

Dragging around some error status codes is not worth the extra complexity.

Just mount the exe as a harddrive instead, it also includes automatic startup-sequence generation if single exe is mounted.

10 August 2010, 13:37	#1
thomas Registered User Join Date: Jan 2002 Location: Germany Posts: 7,002	exe-file-in-df0 does not work with assembly winner Download demo from http://www.scene.org/file.php?file=%...n.lha&fileinfo unpack it to Windows directory, insert exe into WinUAE's DF0 -> does not boot. Examining the "disk" from Workbench reveals that it contains all zereos, no file, no bootblock, no data. It works well with other exe files, for example the Assign command from the Workbench disk. DF0 then contains a bootblock, s/startup-sequence and runme.exe as expected.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Elbox Winner ZIV Busboard Questions...	Info-Seeker	support.Hardware	2	11 June 2010 10:35
If WinUAE cannot detect your supposedly empty HDD, look for zap.exe or wipe.exe.	fmcpma	support.WinUAE	5	08 August 2006 00:35
Winner Z4 busboard for sale	Boot_WB	MarketPlace	8	11 July 2006 13:34
Winner IDE	dir_marillion	support.Hardware	10	06 February 2006 14:49
FS: A1200 Zorro IV Busboard/Winner	maxmouse	MarketPlace	2	16 April 2004 21:10

10 August 2010, 13:43	#2
TCD HOL/FTP busy bee Join Date: Sep 2006 Location: Germany Age: 46 Posts: 31,662	Had the same 'problem' with other (demo) exe files that are bigger than the standard 880k disk. Guess it works as intended.

10 August 2010, 15:14	#5
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,526	It is bonus feature that works and nothing more is needed. (next feature request would be: somehow detect if setpatch is needed and so on, it would never end..)

10 August 2010, 15:25	#6
thomas Registered User Join Date: Jan 2002 Location: Germany Posts: 7,002	What about the "this Kickstart needs 68020 or better" message? Isn't this bonus feature, too? "This file is too big for a floppy drive" is very similar IMHO.

10 August 2010, 15:57	#8
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,526	Important question is: When should it complain about too big exe? If it does not fit in 880k image? But what if selected KS does support HD disk? Should it automatically switch to HD floppy mode (including possible unexpected side-effects) and only complain if it does not fit in HD disk? "Image is too big" isn't the only problem.

14 August 2010, 09:59	#10
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,526	I checked the code and problem is simple: code that "inserts" the disk must not open any GUI dialogs (It is used for all kinds of disk insert tasks, for example configuration file disk inserts) Dragging around some error status codes is not worth the extra complexity. Just mount the exe as a harddrive instead, it also includes automatic startup-sequence generation if single exe is mounted.

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)