Re: [Freedos-devel] FDISK issue

2021-07-13 Thread Wilhelm Spiegl
rge.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 ständig diese Fehler bei

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 ständig diese Fehler beim Ausführen von Format - und plötzlich sind sie

Re: [Freedos-devel] FDISK issue

2021-07-12 Thread Wilhelm Spiegl
edos-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,

Re: [Freedos-devel] FDISK issue

2021-07-10 Thread Wilhelm Spiegl
edos-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 F

Re: [Freedos-devel] FDISK issue

2021-07-10 Thread Wilhelm Spiegl
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

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 prese

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)

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, c

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

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

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 > Th

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 >

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

Re: [Freedos-devel] FDISK issue

2016-01-04 Thread Antony Gordon
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

Re: [Freedos-devel] FDISK issue

2016-01-04 Thread Jerome E. Shidel Jr.
> 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] directiv