subject:"Re\: \[Freedos\-devel\] FDISK issue"

Re: [Freedos-devel] FDISK issue

2021-07-13 Thread Wilhelm Spiegl

Hi,

first of all I want to apologize myself. I didn't want to send this mail to everyone but only to one person.

As a second: I use this mail account for more than ten years and never had problems as you described. It is an online US mail account named: mail.com

As a third: I had problems with formatting hard drives smaller than 500 MB with virtualbox and qemu. Format refused to work. For reasons I cannot reproduce these problems disappeared from one moment to the other.

As a fourth: I just created a virtual HD with FreeDOS but formatted it with Win10 format. After booting the CHS messages also appear. So it cannot be

a problem with FD fdisk or FD format as I thought before.

Sorry, hope this upper text will appear fine now.

W. Spiegl

Sent: Tuesday, July 13, 2021 at 4:08 AM
From: "Thomas Mueller"
To: freedos-devel@lists.sourceforge.net
Subject: Re: [Freedos-devel] FDISK issue

from Wilhelm Spiegl:

[-- Attachment #1 --]
[-- Type: text/html, Encoding: 7bit, Size: 8.2K --]
Content-Type: text/html; charset=UTF-8

Hallo Eric,

ich verstehe es einfach nicht: Erst erhalte ich unter Qemu und Virtualbox stndig diese Fehler beim Ausfhren von Format - und pltzlich sind sie weg.

Was bedeuten diese Error 36, und 129 sowie

+***bad sectors: 1 (code 0x201) on WRITE

+***bad sectors: 1 (code 0x201) on READ

One of the first 5 sectors is broken. Format not possible

bzw. unknown unit for driver

Wie knnen solche Fehler in einer vhd passieren? Ich arbeite mit SSD-Festplatten. Wo kann ich bei der Fehlersuche ansetzen?

Bei der Suche ist mir aufgefallen, da ich bei mehreren Festplatten im System mit jeweils einer primren Partition mit fdisk ALLE Festplatten auf

AKTIV setzen kann, ohne da sich FreeDOS daran strt. Das war mir neu. Es startet einfach von der ersten Festplatte im System.

Gru

Willi

This is a nuisance to read, HTML where most of the messages are plain-text.

I could separate the HTML portion into a file and view with a text-mode (lynx or elinks) or graphical browser, but don't see why I should make that extra effort.

Tom

___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FDISK issue

2021-07-12 Thread Thomas Mueller

from  Wilhelm Spiegl:

[-- Attachment #1 --]  
[-- Type: text/html, Encoding: 7bit, Size: 8.2K --]
Content-Type: text/html; charset=UTF-8

Hallo Eric,

ich verstehe es einfach nicht: Erst erhalte ich unter Qemu und Virtualbox 
stndig diese Fehler beim Ausfhren von Format - und pltzlich 
sind sie weg.

Was bedeuten diese Error 36, und 129 sowie

   
+***bad sectors: 1 (code 0x201) on WRITE

+***bad sectors: 1 (code 0x201) on READ

One of the first 5 sectors is broken. Format not possible

bzw. unknown unit for driver

Wie knnen solche Fehler in einer vhd passieren? Ich arbeite mit 
SSD-Festplatten. Wo kann ich bei der Fehlersuche ansetzen?

 

Bei der Suche ist mir aufgefallen, da ich bei mehreren Festplatten 
im System mit jeweils einer primren Partition mit fdisk ALLE Festplatten 
auf

AKTIV setzen kann, ohne da sich FreeDOS daran strt. Das war 
mir neu. Es startet einfach von der ersten Festplatte im System.



Gru



Willi
  

This is a nuisance to read, HTML where most of the messages are plain-text.

I could separate the HTML portion into a file and view with a text-mode (lynx 
or elinks) or graphical browser, but don't see why I should make that extra 
effort.


Tom



___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FDISK issue

2021-07-12 Thread Wilhelm Spiegl

Hallo Eric,

ich verstehe es einfach nicht: Erst erhalte ich unter Qemu und Virtualbox ständig diese Fehler beim Ausführen von Format - und plötzlich sind sie weg.

Was bedeuten diese Error 36, und 129 sowie

+***bad sectors: 1 (code 0x201) on WRITE

+***bad sectors: 1 (code 0x201) on READ

One of the first 5 sectors is broken. Format not possible

bzw. unknown unit for driver

Wie können solche Fehler in einer vhd passieren? Ich arbeite mit SSD-Festplatten. Wo kann ich bei der Fehlersuche ansetzen?

Bei der Suche ist mir aufgefallen, daß ich bei mehreren Festplatten im System mit jeweils einer primären Partition mit fdisk ALLE Festplatten auf

AKTIV setzen kann, ohne daß sich FreeDOS daran stört. Das war mir neu. Es startet einfach von der ersten Festplatte im System.

Gruß

Willi

Sent: Sunday, July 11, 2021 at 12:16 AM
From: "Wilhelm Spiegl"
To: freedos-devel@lists.sourceforge.net
Subject: Re: [Freedos-devel] FDISK issue

Sorry for disturbing once again.

The vhd formatted by Windows 10 (FAT) Nr. 2 does not give out an error message when booting without fdconfig / fdautoexec.bat.

Willi

Beer will follow now!

Sent: Sunday, July 11, 2021 at 12:02 AM
From: "Wilhelm Spiegl"
To: freedos-devel@lists.sourceforge.net
Subject: Re: [Freedos-devel] FDISK issue

Now it becomes absolutely confusing:

format d: /u says:

Full formatting (wiping all data)

Zapping / checking 443889 sectors and after a standard message

[Error 36]

I repeated with format d: /u /d:

FAT1x size: 217, using FAT16

Disk size 217MBytes, FAT16

[debug] enabled accessing flags

...

Full formatting (wiping all data)

Zapping / checking 443889 sectors and after a standard message

+***bad sectors: 1 (code 0x201) on WRITE

+***bad sectors: 1 (code 0x201) on READ

One of the first 5 sectors is broken. Format not possible

Repeated once again:

format d: /q /d

...

Warning: Resets cluster marks, if any

File system creation

Boot sector -> 0

Drive_IO (Write 0 Count 1) [FAT12/16] (drive d)

critical error during DOS disk access

DOS driver error (hex):01

Description: Unknown unit for driver

Program terminated

Same problem with 484 MB partition (other virtual machine).

Format d:

/q /u exits with error 129,

/u exits with error 36,

/y exits with error 129,

/q /d with the unknown unit for driver

/u /d with the bad sectors

When removing the vhd from virtualbox and adding the vhd as hd at Win10 it asks for formatting.

Windows HD manager says: 484 MB RAW, no failures, active, primary partition, so these settings seem to be correct.

After formatting by Windows 10 the vhd works fine in FD as drive d. I added files an ran chkdsk, no problem.

Win-result: 507.535.360 Bytes,

8.192 Bytes per cluster,

61955 total clusters

If I have a little time I will try if the problem also occurs with the first HD when creating a partition from diskette.

Willi

Cheers! But with more alcohol (5 percent - no ... water...now!)

Sent: Saturday, July 10, 2021 at 10:38 PM
From: "Eric Auer"
To: freedos-devel@lists.sourceforge.net
Subject: Re: [Freedos-devel] FDISK issue

Hi!

> Boot sector unreadable, disk not yet formatted.

You can skip that check by explicitly requesting a
not undoable formatting, see FORMAT /? and use /U
or better /Q /U for quick unconditional format.

> Cannot find existing format - Not saving UNFORMAT data. Please enter
> volume label (none) etc. No label, disk will have no creation timestamp.
> Quick formatting (only flushing metadata)
> Warning, resets bad cluster markings, if any
> DRIVE_IO (WRITE 0, count 1) [FAT12(16] [drive D*]
> Critical error during DOS disk access
> DOS driver error (hex):01
> Description: unknown unit for driver
> Program terminated.
> [Error 129]

So it tries to use FAT16 access for FAT32 drives?

As you say /D made no difference, did /D display
useful extra details? D for debug mode, that is.

If I understand you correctly, you tried to make
tha partition FAT32 in FDISK? Have you checked if
it worked by looking at the FDISK status after a
reboot?

> format version is 0.91w
> Same results with format d: /d

This version is the first which uses OpenWatcom C,
can you check whether FORMAT 0.91v works better?

> If I do the same with a bigger virtual HD (ca. 550 MB size) fdisk
> creates a FAT32 partition and format has NO problems.
> I tried both two times.
>
> Any ideas? Is it reproducable?

As said, please compare FORMAT 0.91v here. You should
also ask WHICHFAT D: to see which partition type the
DOS kernel wants for D: or you could even check whether
using a non-FreeDOS kernel makes a difference for you.

Whichfat: https://auersoft.eu/soft/specials/

Format 0.91v: https://auersoft.eu/soft/by-others/

Regards, Eric

___
Freedos-devel mailing list
Freedos

Re: [Freedos-devel] FDISK issue

2021-07-10 Thread Wilhelm Spiegl

Sorry for disturbing once again.

The vhd formatted by Windows 10 (FAT) Nr. 2 does not give out an error message when booting without fdconfig / fdautoexec.bat.

 

Willi

 

Beer will follow now!

 
 

Sent: Sunday, July 11, 2021 at 12:02 AM
From: "Wilhelm Spiegl" 
To: freedos-devel@lists.sourceforge.net
Subject: Re: [Freedos-devel] FDISK issue



Now it becomes absolutely confusing:

format d: /u says:

Full formatting (wiping all data)

Zapping / checking 443889 sectors and after a standard message

 

[Error 36]

 

I repeated with format d: /u /d:

FAT1x size: 217, using FAT16

Disk size 217MBytes, FAT16

[debug] enabled accessing flags

...


Full formatting (wiping all data)

Zapping / checking 443889 sectors and after a standard message


+***bad sectors: 1 (code 0x201) on WRITE

+***bad sectors: 1 (code 0x201) on READ

One of the first 5 sectors is broken. Format not possible

 

Repeated once again:

format d: /q /d

...

Warning: Resets cluster marks, if any

File system creation

Boot sector -> 0

Drive_IO (Write 0 Count 1) [FAT12/16] (drive d)

critical error during DOS disk access

DOS driver error (hex):01

Description: Unknown unit for driver

Program terminated

 

Same problem with 484 MB partition (other virtual machine).

 

Format d:

/q /u exits with error 129,

/u exits with error 36,

/y exits with error 129,

/q /d with the unknown unit for driver

/u /d with the bad sectors

 

When removing the vhd from virtualbox and adding the vhd as hd at Win10 it asks for formatting.

Windows HD manager says: 484 MB RAW, no failures, active, primary partition, so these settings seem to be correct.

After formatting by Windows 10 the vhd works fine in FD as drive d. I added files an ran chkdsk, no problem.

Win-result: 507.535.360 Bytes,

8.192 Bytes per cluster,

61955 total clusters

 

 

 

 

If I have a little time I will try if the problem also occurs with the first HD when creating a partition from diskette.

 

Willi

 

Cheers! But with more alcohol (5 percent - no ... water...now!)

 

 

 
 

Sent: Saturday, July 10, 2021 at 10:38 PM
From: "Eric Auer" 
To: freedos-devel@lists.sourceforge.net
Subject: Re: [Freedos-devel] FDISK issue


Hi!

> Boot sector unreadable, disk not yet formatted.

You can skip that check by explicitly requesting a
not undoable formatting, see FORMAT /? and use /U
or better /Q /U for quick unconditional format.

> Cannot find existing format - Not saving UNFORMAT data. Please enter
> volume label (none) etc. No label, disk will have no creation timestamp.
> Quick formatting (only flushing metadata)
> Warning, resets bad cluster markings, if any
> DRIVE_IO (WRITE 0, count 1) [FAT12(16] [drive D*]
> Critical error during DOS disk access
>   DOS driver error (hex):01
>   Description: unknown unit for driver
>  Program terminated.
>  [Error 129]

So it tries to use FAT16 access for FAT32 drives?

As you say /D made no difference, did /D display
useful extra details? D for debug mode, that is.

If I understand you correctly, you tried to make
tha partition FAT32 in FDISK? Have you checked if
it worked by looking at the FDISK status after a
reboot?

> format version is 0.91w
> Same results with format d: /d

This version is the first which uses OpenWatcom C,
can you check whether FORMAT 0.91v works better?

> If I do the same with a bigger virtual HD (ca. 550 MB size) fdisk
> creates a FAT32 partition and format has NO problems.
> I tried both two times.
>  
> Any ideas? Is it reproducable?

As said, please compare FORMAT 0.91v here. You should
also ask WHICHFAT D: to see which partition type the
DOS kernel wants for D: or you could even check whether
using a non-FreeDOS kernel makes a difference for you.

Whichfat: https://auersoft.eu/soft/specials/

Format 0.91v: https://auersoft.eu/soft/by-others/

Regards, Eric




___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel




___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel


___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FDISK issue

2021-07-10 Thread Wilhelm Spiegl

Now it becomes absolutely confusing:

format d: /u says:

Full formatting (wiping all data)

Zapping / checking 443889 sectors and after a standard message

 

[Error 36]

 

I repeated with format d: /u /d:

FAT1x size: 217, using FAT16

Disk size 217MBytes, FAT16

[debug] enabled accessing flags

...


Full formatting (wiping all data)

Zapping / checking 443889 sectors and after a standard message


+***bad sectors: 1 (code 0x201) on WRITE

+***bad sectors: 1 (code 0x201) on READ

One of the first 5 sectors is broken. Format not possible

 

Repeated once again:

format d: /q /d

...

Warning: Resets cluster marks, if any

File system creation

Boot sector -> 0

Drive_IO (Write 0 Count 1) [FAT12/16] (drive d)

critical error during DOS disk access

DOS driver error (hex):01

Description: Unknown unit for driver

Program terminated

 

Same problem with 484 MB partition (other virtual machine).

 

Format d:

/q /u exits with error 129,

/u exits with error 36,

/y exits with error 129,

/q /d with the unknown unit for driver

/u /d with the bad sectors

 

When removing the vhd from virtualbox and adding the vhd as hd at Win10 it asks for formatting.

Windows HD manager says: 484 MB RAW, no failures, active, primary partition, so these settings seem to be correct.

After formatting by Windows 10 the vhd works fine in FD as drive d. I added files an ran chkdsk, no problem.

Win-result: 507.535.360 Bytes,

8.192 Bytes per cluster,

61955 total clusters

 

 

 

 

If I have a little time I will try if the problem also occurs with the first HD when creating a partition from diskette.

 

Willi

 

Cheers! But with more alcohol (5 percent - no ... water...now!)

 

 

 
 

Sent: Saturday, July 10, 2021 at 10:38 PM
From: "Eric Auer" 
To: freedos-devel@lists.sourceforge.net
Subject: Re: [Freedos-devel] FDISK issue


Hi!

> Boot sector unreadable, disk not yet formatted.

You can skip that check by explicitly requesting a
not undoable formatting, see FORMAT /? and use /U
or better /Q /U for quick unconditional format.

> Cannot find existing format - Not saving UNFORMAT data. Please enter
> volume label (none) etc. No label, disk will have no creation timestamp.
> Quick formatting (only flushing metadata)
> Warning, resets bad cluster markings, if any
> DRIVE_IO (WRITE 0, count 1) [FAT12(16] [drive D*]
> Critical error during DOS disk access
>   DOS driver error (hex):01
>   Description: unknown unit for driver
>  Program terminated.
>  [Error 129]

So it tries to use FAT16 access for FAT32 drives?

As you say /D made no difference, did /D display
useful extra details? D for debug mode, that is.

If I understand you correctly, you tried to make
tha partition FAT32 in FDISK? Have you checked if
it worked by looking at the FDISK status after a
reboot?

> format version is 0.91w
> Same results with format d: /d

This version is the first which uses OpenWatcom C,
can you check whether FORMAT 0.91v works better?

> If I do the same with a bigger virtual HD (ca. 550 MB size) fdisk
> creates a FAT32 partition and format has NO problems.
> I tried both two times.
>  
> Any ideas? Is it reproducable?

As said, please compare FORMAT 0.91v here. You should
also ask WHICHFAT D: to see which partition type the
DOS kernel wants for D: or you could even check whether
using a non-FreeDOS kernel makes a difference for you.

Whichfat: https://auersoft.eu/soft/specials/

Format 0.91v: https://auersoft.eu/soft/by-others/

Regards, Eric




___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel


___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FDISK issue

2021-07-10 Thread Jerome Shidel

Hi Eric,

Just some info I left out…

My test was on Pentium Pro to reproduce the 230mb FDISK/FORMAT issue...

Kernel 2042, with FAT32
FreeCOM 0.84-pre2 
FDISK 1.3.4
Format 0.91w

A bunch of drivers running…
JEMMEX
LBACACHE
UDVD2
SUSCDEX
DOSLFN
3COM Packet Driver
DHCP setup
no mouse driver at present. 

Worked fine for me.

Wonder what was the size of the second virtual disk. 

Oh, once again… both disks in the Pentium Pro look like 8GB drives. 

(-:

Jerome






___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FDISK issue

2021-07-10 Thread Eric Auer


Hi!

> Boot sector unreadable, disk not yet formatted.

You can skip that check by explicitly requesting a
not undoable formatting, see FORMAT /? and use /U
or better /Q /U for quick unconditional format.

> Cannot find existing format - Not saving UNFORMAT data. Please enter
> volume label (none) etc. No label, disk will have no creation timestamp.
> Quick formatting (only flushing metadata)
> Warning, resets bad cluster markings, if any
> DRIVE_IO (WRITE 0, count 1) [FAT12(16] [drive D*]
> Critical error during DOS disk access
>   DOS driver error (hex):01
>   Description: unknown unit for driver
>  Program terminated.
>  [Error 129]

So it tries to use FAT16 access for FAT32 drives?

As you say /D made no difference, did /D display
useful extra details? D for debug mode, that is.

If I understand you correctly, you tried to make
tha partition FAT32 in FDISK? Have you checked if
it worked by looking at the FDISK status after a
reboot?

> format version is 0.91w
> Same results with format d: /d

This version is the first which uses OpenWatcom C,
can you check whether FORMAT 0.91v works better?

> If I do the same with a bigger virtual HD (ca. 550 MB size) fdisk
> creates a FAT32 partition and format has NO problems.
> I tried both two times.
>  
> Any ideas? Is it reproducable?

As said, please compare FORMAT 0.91v here. You should
also ask WHICHFAT D: to see which partition type the
DOS kernel wants for D: or you could even check whether
using a non-FreeDOS kernel makes a difference for you.

Whichfat: https://auersoft.eu/soft/specials/

Format 0.91v: https://auersoft.eu/soft/by-others/

Regards, Eric




___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FDISK issue

2021-07-10 Thread Jerome Shidel

hi,

> On Jul 10, 2021, at 4:03 PM, Wilhelm Spiegl  wrote:
> 
> one more problem with fdisk 1.3.4:
>  
> I just tried to create a ca. 230 MB big partition on a second HD in 
> virtualbox. I ran fdisk 1.3.4 from the first virtual HD (C:) and executed it 
> for the second HD via
> fdisk position 5, change HD, created one primary partition, everything seems 
> to work fine. I answered the question for FAT32 with YES
> After a reboot (yes, I know this) format d: format 0.91w gave out the 
> following message:
> Boot sector unreadable, disk not yet formatted.
> Cannot find existing format - Not saving UNFORMAT data. Please enter volume 
> label (none) etc. No label, disk will have no creation timestamp.
> Quick formatting (only flushing metadata)
> Warning, resets bad cluster markings, if any
> DRIVE_IO (WRITE 0, count 1) [FAT12(16] [drive D*]
> Critical error during DOS disk access
>   DOS driver error (hex):01
>   Description: unknown unit for driver
>  Program terminated.
>  [Error 129]
>  
> format version is 0.91w
> Same results with format d: /d
>  
> If I do the same with a bigger virtual HD (ca. 550 MB size) fdisk creates a 
> FAT32 partition and format has NO problems.
> I tried both two times.
>  
> Any ideas? Is it reproducable?
>  
> W. Spiegl / Fritz
>  

Real hardware test…
Boot FreeDOS floppy on Pentium Pro.
Wiped MBR on disk #2
Rebooted Floppy
fdisk (no options)
enable FAT32? Y
Change disk #2
Create Primary DOS partition at 230mb
(Shows it made 235mb, FAT16)
Reboot floppy
format d:

WARNING: ALL DATA ON NON-REMOVABLE DISK
DRIVE D: WILL BE LOST! PLEASE CONFIRM!
Proceed with format(YES/NO)? YES
## Boot sector unreadable, disk not yet formated
Disk size: 235 MB, FAT16. ***
Cannot find existing format  - not saving UNFORMAT data.
Please enter volume lane (max. 11 chars):
No label, disk will have no creation timestamp.
QuickFormating (only flushing metadata)
Warning: Resets bad cluster marks if any.
Preparing FAT area…
100 percent complete.
246,726,144 bytes total disk space (disk size)
246,464,512 bytes available on disk (free clusters)
4,096 bytes in each allocation unit.
60,172 allocation units on disk.
Volume Serial Number is 2C52-17F4

Reboot without floppy.
MS-DOS 6.2 started.

echo.>d:test
dir d:
Volume in drive D: has no label
Volume Serial Number is 2C52-17F4
Directory of D:\
TEST 2 07-10-21 4:24p
1 file(s) 2 bytes
246,460,416 bytes free.

All seems as it should.

:-)

Jerome

___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FDISK issue

2021-07-10 Thread Wilhelm Spiegl

one more problem with fdisk 1.3.4:

I just tried to create a ca. 230 MB big partition on a second HD in virtualbox. I ran fdisk 1.3.4 from the first virtual HD (C:) and executed it for the second HD via

fdisk position 5, change HD, created one primary partition, everything seems to work fine. I answered the question for FAT32 with YES

After a reboot (yes, I know this) format d: format 0.91w gave out the following message:

Boot sector unreadable, disk not yet formatted.

Cannot find existing format - Not saving UNFORMAT data. Please enter volume label (none) etc. No label, disk will have no creation timestamp.

Quick formatting (only flushing metadata)

Warning, resets bad cluster markings, if any

DRIVE_IO (WRITE 0, count 1) [FAT12(16] [drive D*]

Critical error during DOS disk access

DOS driver error (hex):01

Description: unknown unit for driver

Program terminated.

[Error 129]

format version is 0.91w

Same results with format d: /d

If I do the same with a bigger virtual HD (ca. 550 MB size) fdisk creates a FAT32 partition and format has NO problems.

I tried both two times.

Any ideas? Is it reproducable?

W. Spiegl / Fritz

Sent: Saturday, July 10, 2021 at 8:33 PM
From: "Jerome Shidel"
To: "FreeDOS Developers"
Subject: [Freedos-devel] FDISK issue

Hi all,

I’ve just noticed a minor issue/wierdness with FDISK.

It is not a serious problem. It is just something it does not do that the Microsoft version does do. Mostly just a little interesting.

Some back story… Several years ago, I took my Pentium Pro motherboard out of it’s original massive 3 foot tall full tower server case and stuck it into a 2U rack mount chassis. But, this forced me to use a PCI riser and only PCI cards. Well, a few days ago I was fed up with trying to get good sound support with the mostly working PCI sound card. So, I ripped it out of that case, grabbed some other components I had laying around and stuffed it into a different modern full tower case (only 19” tall). Pulled my Sound Blaster AWE64 Gold card out of the 486 docking station and plugged it into one of the Pentium Pro’s ISA slots. Yippie, good sound in DOS games.

I mainly use the machine for testing stuff. But, I’ve got a lot of games and software from the Win 9X days. So, I’m going to set it up for booting FreeDOS, MS-DOS, PC-DOS, DR-DOS, OpenDOS, Win98SE. Maybe even do different versions like PC-DOS 7/2000, MS-DOS 3.3/5.0/6.22, etc.

The first step in this process was to install MS-DOS 6.2. Which, I decided to record as a video.

The Pentium Pro has two hard disk drives. A #1-160GB and a #2-40GB, both are seen by the BIOS as 8GB. Under DOS, they work fine this way as 8GB drives. (Under linux, their full capacity is available).

To my surprise, the MS-DOS installer automatically partitioned and formatted both drives. The #2 drive is very slow. Also, I don’t really even want it visible under MS-DOS.

Now we’ll get into the issue I noticed...

So, I zero’d the MBR on hard disks #1 & #2.
Booted FreeDOS and ran FDISK 1.3.4.
Created an extended partition on #2 using all space (8040mb FAT32)
Rebooted MS-DOS installer.
It partitioned and reboot.
It automatically started formatting drive C:
Then formatted drive D:, huh?
Quit setup program and launched MS 6.2’s FDISK.
Drive C: Fine.
Partition C: 1, PRI DOS, 2047mb, FAT16, 26%
Total disk space is 8025 Mbytes (1 Mbyte = 1048576 bytes)
Drive D: Is a little interesting.
Partition 1, Non-DOS, 8033mb, 100% usage
Partition 2, PRI DOS, 8mb, 0% usage
Total disk space is 8025 Mbytes (1 Mbyte = 1048576 bytes)
Interesting that MS created a 8mb partition, when the Non-DOS partition is already using 8mb more than the disk has available.
Rebooted FreeDOS.
Ran FDISK.
Deleted the Drive #2, partition #2, PRI DOS FAT 12 partition.
Could not create a new partition.
Rebooted and ran MS installer, it repartitioned D: adding the 8mb FAT12 Partition.
Ran FreeDOS FDISK under MS-DOS. Reports:
Drive 1
Partition C: 1, Active, PRI DOS, NO NAME, 2055mb, FAT16, 26%
Total space 8048mb
Drive 2
Partition 1, EXT DOS, 8040mb, Extended, 100%
Partition D: 2, PRI DOS, 16mb, FAT12, 0%
Total space 8048mb
Logical… Drive E:, 8040mb, FAT32ext, 100%

To summarize… While all the numbers are different and neither seem to add up, the main difference was Microsoft’s FDISK was utilizing that little bit of extra space and the “end” of disk #2.

Strange.

:-)

Jerome

___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FDISK issue

2016-01-05 Thread Antony Gordon

Hi,

'default' is a keyword. I am also reworking the makefile so that hopefully
it will rebuild outside of the environment, then I'll work on OW
compatibility and maybe even Pacific C as well.

On Mon, Jan 4, 2016 at 7:01 PM Rugxulo  wrote:

> Hi,
>
> On Mon, Jan 4, 2016 at 9:54 AM, Antony Gordon  wrote:
> >
> > I’m attempting to recompile FDISK and apparently you need to assemble
> bootnorm.asm
> > and booteasy.asm and I’m getting this error when assembling booteasy.asm
> >
> > booteasy.asm:260: error: invalid parameter to [default] directive
> >  This is line 260 below.
> >
> > default db  '?',' '+80h
> >
> > Any thoughts?
>
> The two .ASM files are both dated 2002. Inside BOOTEASY.ASM, it says
> "Ported to NASM by Tom Ehlert". IIRC, the last of the pre-2.x series
> of NASM (i.e. 0.98.39, without AMD64 support) was released in 2005.
> Some older tools obviously used (or even still require) older versions
> of NASM. E.g. SHSURDRV requires 0.98.39 (32-bit for more RAM) and
> won't work in newer due to incompatible macros.
>
> So, worst case scenario, just use old 0.98.39 and don't worry about it:
>
> 1).
> http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/devel/asm/nasm/0.98.39/
>
> 2a).
> http://sourceforge.net/projects/nasm/files/DOS%2032-bit%20binaries/0.98.39/nasm-0.98.39-djgpp.zip/download
> 2b
> ).
>
> http://sourceforge.net/projects/nasm/files/DOS%2016-bit%20binaries%20%28OBSOLETE%29/0.98.39/nsm09839.zip/download
>
>
> --
> ___
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel
>
--
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FDISK issue

2016-01-04 Thread Jerome E. Shidel Jr.


> On Jan 4, 2016, at 4:09 PM, Antony Gordon  wrote:
> 
> Hi,
> 
> I’m using NASM. It seems to work well with all the other labels. 
> 
> In my digging, I have found that default may be a keyword. I’ll try that too 
> just to be sure.

I think you are correct that it is a keyword. (I’ve never used it)

So, just do a search, replace and pray with something like defopt

But labels really do need that : 

Nash always complains that “a label alone on a line without a colon may be in 
error”

It is really useful when you type something like “jump OverInfiniteLoop"

:-)

> 
> -T
>> On Jan 4, 2016, at 4:07 PM, Jerome E. Shidel Jr.  wrote:
>> 
>> 
>>> On Jan 4, 2016, at 10:54 AM, Antony Gordon  wrote:
>>> 
>>> Hi,
>>> 
>>> I’m attempting to recompile FDISK and apparently you need to assemble 
>>> bootnorm.asm and booteasy.asm and I’m getting this error when assembling 
>>> booteasy.asm
>>> 
>>> booteasy.asm:260: error: invalid parameter to [default] directive
>>> This is line 260 below.
>>> 
>>> default db  '?',' '+80h
>>> 
>>> Any thoughts?
>> 
>> Yep. What assembler are you using?
>> 
>> default looks like it should be a label.
>> 
>> in nasm you would require a colon to inform the compiler it is label. like 
>> this
>> 
>> default: db …….
>> 
>>> 
>>> -T
>>> --
>>> ___
>>> Freedos-devel mailing list
>>> Freedos-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/freedos-devel
>> 
>> 
>> --
>> ___
>> Freedos-devel mailing list
>> Freedos-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freedos-devel
> 
> 
> --
> ___
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel


--
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FDISK issue

2016-01-04 Thread Louis Santillan

You'll likely need MASM or TASM to assemble.  WASM/JWASM may work in
compatibility mode.

On Mon, Jan 4, 2016 at 1:09 PM, Antony Gordon  wrote:

> Hi,
>
> I’m using NASM. It seems to work well with all the other labels.
>
> In my digging, I have found that default may be a keyword. I’ll try that
> too just to be sure.
>
> -T
> > On Jan 4, 2016, at 4:07 PM, Jerome E. Shidel Jr. 
> wrote:
> >
> >
> >> On Jan 4, 2016, at 10:54 AM, Antony Gordon  wrote:
> >>
> >> Hi,
> >>
> >> I’m attempting to recompile FDISK and apparently you need to assemble
> bootnorm.asm and booteasy.asm and I’m getting this error when assembling
> booteasy.asm
> >>
> >> booteasy.asm:260: error: invalid parameter to [default] directive
> >> This is line 260 below.
> >>
> >> default db  '?',' '+80h
> >>
> >> Any thoughts?
> >
> > Yep. What assembler are you using?
> >
> > default looks like it should be a label.
> >
> > in nasm you would require a colon to inform the compiler it is label.
> like this
> >
> > default:  db …….
> >
> >>
> >> -T
> >>
> --
> >> ___
> >> Freedos-devel mailing list
> >> Freedos-devel@lists.sourceforge.net
> >> https://lists.sourceforge.net/lists/listinfo/freedos-devel
> >
> >
> >
> --
> > ___
> > Freedos-devel mailing list
> > Freedos-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/freedos-devel
>
>
>
> --
> ___
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel
>
--
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FDISK issue

2016-01-04 Thread Rugxulo

Hi,

On Mon, Jan 4, 2016 at 9:54 AM, Antony Gordon  wrote:
>
> I’m attempting to recompile FDISK and apparently you need to assemble 
> bootnorm.asm
> and booteasy.asm and I’m getting this error when assembling booteasy.asm
>
> booteasy.asm:260: error: invalid parameter to [default] directive
>  This is line 260 below.
>
> default db  '?',' '+80h
>
> Any thoughts?

The two .ASM files are both dated 2002. Inside BOOTEASY.ASM, it says
"Ported to NASM by Tom Ehlert". IIRC, the last of the pre-2.x series
of NASM (i.e. 0.98.39, without AMD64 support) was released in 2005.
Some older tools obviously used (or even still require) older versions
of NASM. E.g. SHSURDRV requires 0.98.39 (32-bit for more RAM) and
won't work in newer due to incompatible macros.

So, worst case scenario, just use old 0.98.39 and don't worry about it:

1). 
http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/devel/asm/nasm/0.98.39/

2a). 
http://sourceforge.net/projects/nasm/files/DOS%2032-bit%20binaries/0.98.39/nasm-0.98.39-djgpp.zip/download
2b). 
http://sourceforge.net/projects/nasm/files/DOS%2016-bit%20binaries%20%28OBSOLETE%29/0.98.39/nsm09839.zip/download

--
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] FDISK issue

Re: [Freedos-devel] FDISK issue

Re: [Freedos-devel] FDISK issue

Re: [Freedos-devel] FDISK issue

Re: [Freedos-devel] FDISK issue

Re: [Freedos-devel] FDISK issue

Re: [Freedos-devel] FDISK issue

Re: [Freedos-devel] FDISK issue

Re: [Freedos-devel] FDISK issue

Re: [Freedos-devel] FDISK issue

Re: [Freedos-devel] FDISK issue

Re: [Freedos-devel] FDISK issue

Re: [Freedos-devel] FDISK issue

13 matches

Site Navigation

Mail list logo

Footer information