date:20161022

Re: [Freedos-devel] Getting ready for FreeDOS 1.2

2016-10-22 Thread Jerome E. Shidel Jr.

Hello Juan,

First, thanks all the information. It definitely should be helpful.

> [..]
>> What host OS are you using?
> openSUSE 11.4

Love openSuSE. (My personal favorite distro!)

> [..]

Based on your information, I have been able to replicate the problem in
VirtualBox as well. Basically, this seems to be a summary of the issue.

A pre-formatted floppy image has no issue being formatted in any mode.

A zero’d image file for a floppy appears to be problematic. A simple test
is to create an a blank image by using “dd bs=512 count=2880 if=/dev/zero 
of=floppy.img”
Then attaching this to a virtual machine and simply formatting with “format a:” 
or 
“format /u a:” terminates with and error code.

However, telling format the image size appears to bypass the issue.
For example, “format /f:1440 a:” appears to always work.

Jerome

--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Getting ready for FreeDOS 1.2

2016-10-22 Thread Juan Manuel Guerrero

Am 22.10.2016 18:08, schrieb Jerome E. Shidel Jr.:
Hello Jerome and all the other interested ones,

[snip]
 > What host OS are you using?
openSUSE 11.4

 > If you booted the CD under VMware and installed FreeDOS,
 > are you still booting the El Torito CD?
Yes.  I forgot to unmount it.  Now I have disconnected the
CD image from the machine and repeated the experiment but the
outcomming is the absolutely the same.

 > Are you running the latest Version of VirtualBox (5.0.28)?
No.  I have _never_ run any version of VirtualBox.
I have used VMware Player  5.0.2 build-1031769 _only_.


 > Have you made major changes from the default VirtualBox settings?
The settings of the WMware Player are:
   1 processor
   64 MB ram
   2 GB  HD
   No CD mounted
   No floppy mounted
   Everything else are default settings that the Player selects.
   I have tried one time using only 4 MB of ram but it had no influence.


 > Have you modified the boot configuration of FreeDOS and is something 
 > conflicting?
No.  The only thing I selected was that only the base packages shall be 
installed.
I have used german as installation language all the time.
No editing neither of fdconfig.sys nor of autoexec.bat at all.  I am using the
virtual machine as it is.  When the machine is booted, the first boot option is
used.  I have never tried any other.

 > Are you sure the actual floppy image is a valid size, exists and is writable 
 > by the host OS?
Yes, I can do:
   dd bs=512 count=2880 if=/dev/zero of=rawfloppy.img
or
   dd if=test.img of=rawfloppy.img
rawfloppy.img is the image created by the virtual machine.
If test.img has a file system then rawfloppy.img can be read by FreeDOS.
The raw floppy image is created by VMware player by selecting the corresponding 
"create" command.
For the VMware Player this is:
   "Edit virtual machine settings"  -->  Hardware-tab:  floppy  -->  
Connection:  "Use a floppy image"  --> "Create..."
The create command does not allow to select or change the size of the image.
Or at least I do not know how.  It creates a raw 1.44 MB image.  This image
can be formated with MSDOS-6.22, Win98SE, Win2K-SP5 and WinXP-SP3.  This means
that I am running different virtual machines created with the same VMware Player
and this Player creates the raw image.
If I use the format program from FreeDOS, this is "format /d a:" then the image
gets ruined and cannot be formated by any of the previously stipulated microsoft
OSes.  If I boot the MSDOS-6.22 virtual machine I am capable to mount and fix 
the
image using my old Norton Utilities.  After that the image can be formated by
MSDOS again.  Of course there is nothing particular about Norton, there are
certainly thousends of other disk tools that will fix the floppy.


 > (maybe download the FD12FLOPPY.zip and try formatting it’s image)
I have done this and it formats flawlessly.  But this is not a surprise at all
because it is not a raw floppy but a formated one.  For an already formated
floppy, the FreeDOS "format /d a:" command always works.  But if I take that
one and ruin the first couple of sectors with the command:
   dd bs=512 count=2880 if=/dev/zero of=FLOPPY.img
then "format /d a:" fails miserably.


It remains a fact, that a raw floppy created by VMware Player  5.0.2 
build-1031769
can be formated by any format program of the microsoft OSes I have tested.
This means that both "format a:" and "format /u a:" work without problems.
But a raw floppy created in the same way by the same virtual machine can only
be formated using the "format /u a:" command but not "format a:" command when
the FreeDOS format program is used.
If the command:
   dd bs=512 count=2880 if=/dev/zero of=FLOPPY.img
is run neither of both MSDOS format nor FreeDOS format program can format the
floppy image.  This means that "format a:" does not work under this condition.
In this case "format /u a:" must be used to get the floppy image fsuccessfully
formated by both OSes.  The conclusion is "format /u a:" will always work but
"format a:" will not.

I do not know if it is really worth to continue investing time in this issue.
This may be a peculiarity of my installation.  I use only VMware Player  5.0.2 
build-1031769
and I have never tried VirtualBox.  VMware Player  5.0.2 build-1031769 is also
quite old and may be a newer version does not exhibit this kind of problem but
due to the lincense politics of VMware for private/home users I have stoped to
update so I cannot tell.


Regards,
Juan M. Guerrero

--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Getting ready for FreeDOS 1.2

2016-10-22 Thread Jerome E. Shidel Jr.

> On Oct 22, 2016, at 1:11 PM, Antony Gordon  wrote:
> 
> Hi,
> 
> Host OS should not matter. If the "gold standard" of MS-DOS works in that 
> configuration with the disk images, there is definitely something that isn't 
> right in this release. For those having a problem, what happens in FreeDOS 
> 1.1.
> 
> Tony
> 
Absolutely, unless there is a Platform specific bug with the VM software, 
default configuration settings and other very OS specific issues. 

For example, image file marked as read-only or writable only by root but 
running as user. When doing testing and such, I once set one of 
the hard disk images to 644 (on purpose) on a Mac. This was a few months back 
and did not behave like I expected. I think it was in
VirtualBox. If I recall correctly, it would act like it was writing to the 
drive but after a while would start throwing errors.

Jerome.--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Getting ready for FreeDOS 1.2

2016-10-22 Thread Antony Gordon

Hi,

Host OS should not matter. If the "gold standard" of MS-DOS works in that
configuration with the disk images, there is definitely something that
isn't right in this release. For those having a problem, what happens in
FreeDOS 1.1.

Tony

On Sat, Oct 22, 2016, 12:10 PM Jerome E. Shidel Jr. 
wrote:

> Hello Juan,
>
> > On Oct 22, 2016, at 7:55 AM, Juan Manuel Guerrero 
> wrote:
> >
> > OFYI: I have tried to format a floppy image with a VMware Player 5.0.2
> using
> > FreeDOS 1.2-pre23 and I have observed the same issue as described for
> VirtualBox.
>
> The FreeDOS 1.2 preview releases are built under FreeDOS 1.2 build
> environment (BE),
> The BE is running under VirtualBox and contains 2 floppy drive images and
> 3 hard disk
> drive images. The USB and CD releases of 1.2 contain a utility FDIDEV.BAT
> that
> will convert a (virtual) machine into a FreeDOS BE. Each preview release
> is built
> automatically using the mkFDI.bat utility that is installed and part of
> the BE. During the
> build process performed by mkFDI, this utility reformats both Floppy
> images and two
> of the hard disk images. It does this to zero out unused portions for
> better disk
> image compression at release time. I have seen no issues formatting any of
> these
> images from FreeDOS inside VirtualBox. Earlier builds (like preview 10 and
> earlier)
> were running inside VMware Fusion. But, VirtualBox performed the build
> many times
> faster. I saw no issues under VMware Fusion either.
>
> Now, just as a quick verification, I duplicated a 1.44 floppy image and
> booted a test
> install of Preview 23 inside VirtualBox 5.0.28. Format reported no
> problems with
> any of the various methods I used to reformat that floppy image.
>
> Other than the errors you are getting towards the end. I see only line
> that differs
> in my debug log.
>
> [DEBUG]  Sector buffer at 0E17:6770, track buffer at 0E17:6B70
>
> This is probably just due to the difference in the virtual machine BIOS.
> Or,
> possibly the booted configuration.
>
> > [..]
> > [DEBUG]  Sector buffer at 1A3F:6770, track buffer at 1A3F:6B70
> > [..]
> > [DEBUG]  FAT Sectors: 1 to 18 ->
> >   0% +**Drive_IO(WRITE 1, count 1 ) [FAT12/16] [drive A*]
> >
> >  Critical error during DOS disk access
> >  DOS driver error (hex): 01
> >Description: unknown unit for driver
> >  Program terminated.
> > [DEBUG]  DOS 7+, UNLOCKing drive (by one level)
> > [DEBUG]  DOS 7+, UNLOCKing drive (by one level)
>
> Just as verification, I have a couple simple questions that you have
> probably already checked.
>
> What host OS are you using?
>
> If you booted the CD under VMware and installed FreeDOS, are you still
> booting the
> El Torito CD?
>
> Are you running the latest Version of VirtualBox (5.0.28)?
>
> Have you made major changes from the default VirtualBox settings?
>
> Have you modified the boot configuration of FreeDOS and is something
> conflicting?
>
> Are you sure the actual floppy image is a valid size, exists and is
> writable by the host OS?
> (maybe download the FD12FLOPPY.zip and try formatting it’s image)
>
> Jerome
>
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> ___
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel
>
-- 

Clumsily typed on a mobile device
--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Getting ready for FreeDOS 1.2

2016-10-22 Thread Maarten Vermeulen

Op zaterdag 22 oktober 2016 heeft Tom Ehlert  het
volgende geschreven:
> Dear Marten!

Haha! Is my name that difficult, you're the 5th person on this list to
write my name wrong. :)


> but:
>
> when changing the topic, please change the subject of your mail

Sorry, didn't think about that... I think I automatically replied on this
one (without thinking that much) because of 'report any bugs', but I should
have done that... Sorry.


> when changing the topic, please don't full quote some topic (keyboard
> layout issues) that is entirely unrelated to your topic.

That should be very logical! No, I am going to make the topic "ever heard
of a living stone?"
While talking about FreeDOS. :)

Wow, that's a bad one.

>
> even dutch kids should follow a minimum of netiquette.

The only thing that happend was me not thinking about a subject. :(
I didn't do anything else. *crying*

Those two were jokes. But why that comment? Should be very very logical.
But that's just me.

Anyway, sorry for not changing the subject.

Maarten





-- 
Founder BirdOS and FeatherCode
--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Getting ready for FreeDOS 1.2

2016-10-22 Thread Jerome E. Shidel Jr.

Hello Juan,

> On Oct 22, 2016, at 7:55 AM, Juan Manuel Guerrero  
> wrote:
> 
> OFYI: I have tried to format a floppy image with a VMware Player 5.0.2 using
> FreeDOS 1.2-pre23 and I have observed the same issue as described for 
> VirtualBox.

The FreeDOS 1.2 preview releases are built under FreeDOS 1.2 build environment 
(BE),
The BE is running under VirtualBox and contains 2 floppy drive images and 3 
hard disk
drive images. The USB and CD releases of 1.2 contain a utility FDIDEV.BAT that 
will convert a (virtual) machine into a FreeDOS BE. Each preview release is 
built 
automatically using the mkFDI.bat utility that is installed and part of the BE. 
During the
build process performed by mkFDI, this utility reformats both Floppy images and 
two
of the hard disk images. It does this to zero out unused portions for better 
disk
image compression at release time. I have seen no issues formatting any of these
images from FreeDOS inside VirtualBox. Earlier builds (like preview 10 and 
earlier) 
were running inside VMware Fusion. But, VirtualBox performed the build many 
times
faster. I saw no issues under VMware Fusion either.

Now, just as a quick verification, I duplicated a 1.44 floppy image and booted 
a test
install of Preview 23 inside VirtualBox 5.0.28. Format reported no problems with
any of the various methods I used to reformat that floppy image.

Other than the errors you are getting towards the end. I see only line that 
differs
in my debug log.

[DEBUG]  Sector buffer at 0E17:6770, track buffer at 0E17:6B70

This is probably just due to the difference in the virtual machine BIOS. Or, 
possibly the booted configuration. 

> [..]
> [DEBUG]  Sector buffer at 1A3F:6770, track buffer at 1A3F:6B70
> [..]
> [DEBUG]  FAT Sectors: 1 to 18 ->
>   0% +**Drive_IO(WRITE 1, count 1 ) [FAT12/16] [drive A*]
> 
>  Critical error during DOS disk access
>  DOS driver error (hex): 01
>Description: unknown unit for driver
>  Program terminated.
> [DEBUG]  DOS 7+, UNLOCKing drive (by one level)
> [DEBUG]  DOS 7+, UNLOCKing drive (by one level)

Just as verification, I have a couple simple questions that you have probably 
already checked.

What host OS are you using?

If you booted the CD under VMware and installed FreeDOS, are you still booting 
the
El Torito CD?

Are you running the latest Version of VirtualBox (5.0.28)?

Have you made major changes from the default VirtualBox settings?

Have you modified the boot configuration of FreeDOS and is something 
conflicting?

Are you sure the actual floppy image is a valid size, exists and is writable by 
the host OS? 
(maybe download the FD12FLOPPY.zip and try formatting it’s image)

Jerome
--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Getting ready for FreeDOS 1.2

2016-10-22 Thread Eric Auer


Hi Juan,

...

>   Full Formatting (wiping all data)
> [DEBUG]  Formatting: Cylinder:  0  Head:  0  Sectors: 18

...

> [DEBUG]  Formatting: Cylinder: 79  Head:  1  Sectors: 18
>   98% 100%
> [DEBUG]  File System Creation
> [DEBUG]  Boot Sector -> 0
> [DEBUG]  FAT Sectors: 1 to 18 ->
>0% +**Drive_IO(WRITE 1, count 1 ) [FAT12/16] [drive A*]
> 
>   Critical error during DOS disk access
>   DOS driver error (hex): 01
> Description: unknown unit for driver
>   Program terminated.
> [DEBUG]  DOS 7+, UNLOCKing drive (by one level)
> [DEBUG]  DOS 7+, UNLOCKing drive (by one level)
> 
> 
>  > C:\>echo %errorlevel%
>  > 129

This sounds a bit like FORMAT, BIOS, drive and DOS kernel cannot
agree about when and how to reset the drive after formatting. On
a real computer, it might have helped to re-insert the disk at
that moment? It may also depend on the kernel version: After the
FORMAT loop, the disk does not yet contain a filesystem, but the
error message happens AFTER writing the boot sector, BEFORE the
FAT and root directory get written, according to the messages...

A workaround would be to write the FAT and root directory using
raw BIOS I/O instead of already switching to DOS I/O after the
boot sector update, any comments from kernel experts? As far as
I remember, using less raw BIOS I/O is generally more "friendly".

Regards, Eric



--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] Getting ready for FreeDOS 1.2

2016-10-22 Thread Juan Manuel Guerrero

OFYI: I have tried to format a floppy image with a VMware Player 5.0.2 using
FreeDOS 1.2-pre23 and I have observed the same issue as described for 
VirtualBox.
If /q/u is used it becomes possible to format the image.  I have also tried
to format using only /d.  See below for the output produced.  What surprises
me is that the format program from MSDOS 6.22 does not require options like
/u/q to format a floppy image on the same virtual machine.  Issuing format a:
just does the job.  For an user that is familiar to MSDOS but not familiar at
all to FreeDOS this deviation in program behavior may be confusing and the user
may have difficulties in formating an image.
Is this different behavior intentional?  IMHO, if FreeDOS claims to be MSDOS
compatible, the deviation in behavior should be as less as possible.  This is
not an issue for me personally.  When I know that there is a difference in
program behavior I can act accordingly but it remains surprising that something
that I expected to be compatible is not always compatible conserning its 
behavior.

Regards,
Juan M. Guerrero



format /d a:

[DEBUG]  FORMAT 0.91v, selected drive A:
[DEBUG]  Sector buffer at 1A3F:6770, track buffer at 1A3F:6B70
[DEBUG]  Skipped ASSIGN check for diskette drive.
[DEBUG]  DOS 7+, LOCKing drive
  Insert new diskette for drive A:
  Insert new disk please,
  Press ENTER when the right disk is in drive...

[DEBUG]  Checking whether we need low-level format.
[DEBUG]  Test-reading boot sector.
  Boot sector contents implausible, disk not yet FAT formatted
[DEBUG]  DOS 7+, FORMAT-LOCKing drive
[DEBUG]  Current Disk Drive Parameter Table Values at 0070:0119:
[DEBUG]  [DDPT] Step Rate: 240 msec  Head Unload:48 msec  DMA Flag Bit:  0
[DEBUG]  [DDPT] Head Load:   4 msec  Post Rotate:  2035 msec  Sector Size: 512
[DEBUG]  [DDPT] SECTORS PER TRACK:  18  (Gap:  27  Data: 255  Format Gap: 108)
[DEBUG]  [DDPT] Fill Char: 0xF6  Head Settle: 15 msec  Motor Start: 625 msec
Using drive default: 1440k (Cyl=80 Head=2 Sec=18)
[DEBUG]  Setting geometry with int 13h ah=18h: tracks=80 sectors=18
[DEBUG] Updated INT 1E (DDPT) data at: 0070:0119.

[DEBUG]  Interleave Map:
1  2  3  4  5  6  7  8  9 10 11 12 13 14 15 16 17 18

[DEBUG]  Configured Disk Drive Parameter Table Values at 0070:0119:
[DEBUG]  [DDPT] Step Rate: 240 msec  Head Unload:48 msec  DMA Flag Bit:  0
[DEBUG]  [DDPT] Head Load:   4 msec  Post Rotate:  2035 msec  Sector Size: 512
[DEBUG]  [DDPT] SECTORS PER TRACK:  18  (Gap:  27  Data: 255  Format Gap: 108)
[DEBUG]  [DDPT] Fill Char: 0xF6  Head Settle: 15 msec  Motor Start: 625 msec
[DEBUG]  Controller setup 17: [configured type 7]  500 kbps (HD 1xx0k)
-- press ENTER to format disk (ESCAPE to abort) --
Cannot find existing format - forcing full format
Please enter volume label (max. 11 chars):

No label, disk will have no creation timestamp.
  Full Formatting (wiping all data)
[DEBUG]  Formatting: Cylinder:  0  Head:  0  Sectors: 18
[DEBUG]  Formatting: Cylinder:  0  Head:  1  Sectors: 18
   0% [DEBUG]  Formatting: Cylinder:  1  Head:  0  Sectors: 18
[DEBUG]  Formatting: Cylinder:  1  Head:  1  Sectors: 18
   1% [DEBUG]  Formatting: Cylinder:  2  Head:  0  Sectors: 18
[DEBUG]  Formatting: Cylinder:  2  Head:  1  Sectors: 18
   2% [DEBUG]  Formatting: Cylinder:  3  Head:  0  Sectors: 18
[DEBUG]  Formatting: Cylinder:  3  Head:  1  Sectors: 18
   3% [DEBUG]  Formatting: Cylinder:  4  Head:  0  Sectors: 18
[DEBUG]  Formatting: Cylinder:  4  Head:  1  Sectors: 18
   5% [DEBUG]  Formatting: Cylinder:  5  Head:  0  Sectors: 18
[DEBUG]  Formatting: Cylinder:  5  Head:  1  Sectors: 18
   6% [DEBUG]  Formatting: Cylinder:  6  Head:  0  Sectors: 18
[DEBUG]  Formatting: Cylinder:  6  Head:  1  Sectors: 18
   7% [DEBUG]  Formatting: Cylinder:  7  Head:  0  Sectors: 18
[DEBUG]  Formatting: Cylinder:  7  Head:  1  Sectors: 18
   8% [DEBUG]  Formatting: Cylinder:  8  Head:  0  Sectors: 18
[DEBUG]  Formatting: Cylinder:  8  Head:  1  Sectors: 18
  10% [DEBUG]  Formatting: Cylinder:  9  Head:  0  Sectors: 18
[DEBUG]  Formatting: Cylinder:  9  Head:  1  Sectors: 18
  11% [DEBUG]  Formatting: Cylinder: 10  Head:  0  Sectors: 18
[DEBUG]  Formatting: Cylinder: 10  Head:  1  Sectors: 18
  12% [DEBUG]  Formatting: Cylinder: 11  Head:  0  Sectors: 18
[DEBUG]  Formatting: Cylinder: 11  Head:  1  Sectors: 18
  13% [DEBUG]  Formatting: Cylinder: 12  Head:  0  Sectors: 18
[DEBUG]  Formatting: Cylinder: 12  Head:  1  Sectors: 18
  15% [DEBUG]  Formatting: Cylinder: 13  Head:  0  Sectors: 18
[DEBUG]  Formatting: Cylinder: 13  Head:  1  Sectors: 18
  16% [DEBUG]  Formatting: Cylinder: 14  Head:  0  Sectors: 18
[DEBUG]  Formatting: Cylinder: 14  Head:  1  Sectors: 18
  17% [DEBUG]  Formatting: Cylinder: 15  Head:  0  Sectors: 18
[DEBUG]  Formatting: Cylinder: 15  Head:  1  Sectors: 18
  18% [DEBUG]  Formatting: Cylinder: 16  Head:  0  Sectors: 18
[DEBUG]  Formatting: Cylinder: 16  Head:  1  Sectors: 18
  20% [DEBUG]  Formatting: Cylinder: 17  Head:  0

Re: [Freedos-devel] Getting ready for FreeDOS 1.2

Re: [Freedos-devel] Getting ready for FreeDOS 1.2

Re: [Freedos-devel] Getting ready for FreeDOS 1.2

Re: [Freedos-devel] Getting ready for FreeDOS 1.2

Re: [Freedos-devel] Getting ready for FreeDOS 1.2

Re: [Freedos-devel] Getting ready for FreeDOS 1.2

Re: [Freedos-devel] Getting ready for FreeDOS 1.2

Re: [Freedos-devel] Getting ready for FreeDOS 1.2

8 matches

Site Navigation

Mail list logo

Footer information