seatools for DOS

[heavytull]

I downloaded the 'seatools for DOS' diskette creator on seagate website. it's a windows program that creates the diskette; so a floppy disk must be present in the drive. running the program is ok, but creating the diskette fails, it says "the current diskette format not valid". while the diskette is blank, vfat, mounted and linked to a: in wine; so everything seems to be ok.

It is same for the win98 DOS program which creates the boot diskette. It seems wine is not handling dos devices nicely, or there might be some misconfiguration somewhere.

[Dan Kegel]

On Thu, Apr 17, 2008 at 2:47 AM, heavytull <[email protected]> wrote:

I downloaded the 'seatools for DOS' diskette creator on seagate website. it's a windows program that creates the diskette; so a floppy disk must be present in the drive. running the program is ok, but creating the diskette fails, it says "the current diskette format not valid". while the diskette is blank, vfat, mounted and linked to a: in wine; so everything seems to be ok.

It is same for the win98 DOS program which creates the boot diskette. It seems wine is not handling dos devices nicely, or there might be some misconfiguration somewhere.

DOS support in Wine is somewhat bitrotted at this point. Please
try using dosemu or one of the other dos emulators -- you'll
probably have better luck.

[felix]

On Thu, Apr 17, 2008 at 04:47:05AM -0500, heavytull wrote:

I downloaded the 'seatools for DOS' diskette creator on seagate
website. it's a windows program that creates the diskette; so a
floppy disk must be present in the drive. running the program is
ok, but creating the diskette fails, it says "the current
diskette format not valid". while the diskette is blank, vfat,
mounted and linked to a: in wine; so everything seems to be ok.

It is same for the win98 DOS program which creates the boot
diskette. It seems wine is not handling dos devices nicely, or
there might be some misconfiguration somewhere.

I don't feel like signing up with Seagate's marketing department just to
get a copy of this to check it out, so I'll have to try taking a stab at
it in the dark .

On the site it sayes that "Seagate for DOS" is a DOS only program and
won't work in Windows. But it also sayes that it runs in it's own OS.
From what you've said, I'm guessing that its actually a Windows
executable that gets downloaded and when run it will write an image to
the floppy disk. You then reboot from that disk and run the tool from
the FreeDOS environment that comes up.

That all said, the idea of writing a floppy image is the key problem.
Having a: symlinked to /media/floppy or wherever else your floppy is
mounted doesn't allow for a raw disk image to be written to the floppy.
Which is exactly what I suspect this program is attempting to do. It
probably has a binary blob that it expects to be able to write directly
to the floppy.

For that it would need to point to the actually floppy device under
/dev, such as /dev/fd0 or /dev/floppy.

The problem is that writing to the mount point, only writes on to the
filesystem on the floppy, where as the most likely senario here is
that it has a floppy image containing a filesystem and files with which
it wants to overwrite the current filesystem and contents on the floppy.

--
Darragh

"Nothing is foolproof to a sufficiently talented fool."

[heavytull]

From what you've said, I'm guessing that its actually a Windows
executable that gets downloaded and when run it will write an image to
the floppy disk. You then reboot from that disk and run the tool from
the FreeDOS environment that comes up.

yes that's it.

That all said, the idea of writing a floppy image is the key problem.

actually tht's the key problem i didn't think about.

Having a: symlinked to /media/floppy or wherever else your floppy is
mounted doesn't allow for a raw disk image to be written to the floppy.

of course!

Which is exactly what I suspect this program is attempting to do. It
probably has a binary blob that it expects to be able to write directly
to the floppy.

probably.

For that it would need to point to the actually floppy device under
/dev, such as /dev/fd0 or /dev/floppy.

yes

i set in wincfg a: pointing to the floppy device. so i could access to the floppy device directly by a: through wine. but unfortunately that doesn't work.
the error message returned is different. it says "couldn't write to a:"

--
Darragh
[/quote]

[pal_gene]

Code: Select all

0019:Call KERNEL32.CreateFileA(001382e8 "\\\\.\\A:",40000000,00000001,00000000,00000003,00000000,00000000) ret=0040320f
0019:trace:file:CreateFileW L"\\\\.\\A:" GENERIC_WRITE FILE_SHARE_READ  creation 3 attributes 0x0
0019:trace:file:RtlDosPathNameToNtPathName_U (L"\\\\.\\A:",0x7dbf7810,(nil),(nil))
0019:trace:file:RtlGetFullPathName_U (L"\\\\.\\A:" 520 0x7dbf7554 (nil))
0019:trace:heap:RtlAllocateHeap (0x110000,00000002,0000001c): returning 0x141680
0019:trace:ntdll:NtCreateFile handle=0x7dbf7818 access=40000000 name=L"\\??\\A:" objattr=00000040 root=(nil) sec=(nil) io=0x7dbf7808 alloc_size=(nil)
attr=00000000 sharing=00000001 disp=1 options=00000050 ea=(nil).0x00000000
0019:trace:heap:RtlAllocateHeap (0x110000,00000002,0000001f): returning 0x144700
0019:trace:heap:RtlFreeHeap (0x110000,00000002,0x144700): returning TRUE
0009: get_window_property( window=0x10028, atom=0000, name=L"PropertySheetInfo" )
0009: get_window_property() = 0 { handle=(nil) }
0019: open_file_object( access=40000000, attributes=00000040, rootdir=(nil), sharing=00000001, options=00000050, filename=L"\\??\\A:" )
0019: open_file_object() = 0 { handle=0x6c }
0019:trace:heap:RtlFreeHeap (0x110000,00000002,0x141680): returning TRUE
0019:trace:file:CreateFileW returning 0x6c
0019:Ret  KERNEL32.CreateFileA() retval=0000006c ret=0040320f
0019:CALL MFC42.800() ret=00403282
0019:Call KERNEL32.InterlockedDecrement(001382dc) ret=5f4018eb
0019:Ret  KERNEL32.InterlockedDecrement() retval=00000000 ret=5f4018eb
0019:RET  MFC42.800() retval=00000000 ret=00403282
0019:Call KERNEL32.DeviceIoControl(0000006c,00070000,00000000,00000000,7dbf7930,00000018,7dbf792c,00000000) ret=00402c29
0019:trace:vxd:DeviceIoControl (0x6c,70000,(nil),0,0x7dbf7930,24,0x7dbf792c,(nil))
0019:trace:ntdll:NtDeviceIoControlFile (0x6c,(nil),(nil),(nil),0x7dbf7850,0x00070000,(nil),0x00000000,0x7dbf7930,0x00000018)
0019:trace:cdrom:CDROM_DeviceIoControl 0x6c IOCTL_CODE_70000 (nil) 0 0x7dbf7930 24 0x7dbf7850

i just have same probs too.
this is trace when accessing floppy device direct through DeviceIoControl, that like program writing disk image to floppy on windows.
i got MessageBox "Unable to determine floppy disk type.".
so i guess it come from failed detect MEDIA TYPE, to prepare.
it seems using CDROM_DeviceIoContol, but i'm not sure wine's internal.

how setup the floppy device correctly?

[heavytull]

how setup the floppy device correctly?

i tried with a: symlinking the floppy device; it doesnt' work either

[Ove Kaaven]

heavytull skrev:

how setup the floppy device correctly?

i tried with a: symlinking the floppy device; it doesnt' work either

For the record, you'd symlink "a:" to the mount point (e.g.
/mnt/floppy), and "a::" to the device (e.g. /dev/fd0). But perhaps there
just isn't enough floppy-disk support in wine for it to work anyway...