Hi!
15--2004 01:16 [EMAIL PROTECTED] (Bernd Blaauw) wrote to
[EMAIL PROTECTED]:
page, previous time I don't found it (if it was present). Also, when planned
2034 release? May be I wait this release and download it completely (instead
patch), if it will be soon?
BB the idea is to test *before*
On Thu, 15 Apr 2004, Arkady V.Belousov wrote:
BB I include this 2034 kernel in the next FreeDOS distribution, next Sunday.
BB there have been a few times where a kernel was released, and a few days
BB later a new kernel followed it because a larger public found a few bugs.
:) Kernel
On Tue, 13 Apr 2004, Arkady V.Belousov wrote:
13-áÐÒ-2004 11:54 [EMAIL PROTECTED] (Bart Oldeman) wrote to
[EMAIL PROTECTED]:
+++ task.c13 Apr 2004 11:54:09 - 1.41
+ fstrcpy(Shell + strlen(Shell), MK_FP(FP_SEG(Config), Config-cfgInitTail));
endp = Shell + strlen(Shell);
Hello Arkady,
AVB Why? To make code more portable between assemblers.
ROTFL
tom
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn
Hi!
13--2004 19:58 [EMAIL PROTECTED] (tom ehlert) wrote to Arkady V.Belousov
[EMAIL PROTECTED]:
AVB Why? To make code more portable between assemblers.
te ROTFL
?
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux
Hello Arkady,
AVB Why? To make code more portable between assemblers.
te ROTFL
AVB ?
Rolling On The Floor Laughing
you really can't keep things untouched?
I would really HATE the kernels assembly sources converted into
GMOUSE cryptographic sources.
tom
Hi!
13--2004 20:30 [EMAIL PROTECTED] (tom ehlert) wrote to Arkady V.Belousov
[EMAIL PROTECTED]:
AVB Why? To make code more portable between assemblers.
te ROTFL
te Rolling On The Floor Laughing
te you really can't keep things untouched?
See the difference: keep untouched or do so or so.
Hi!
12--2004 00:22 [EMAIL PROTECTED] (Bart Oldeman) wrote to
[EMAIL PROTECTED]:
Forged to remove old INITHEADERS. Also, what bad in $(HDR)*.h, why
enumerating .h files is better?
BO It's not better as such, but I'm not sure if * works for all the different
BO make tools we are using. It's
Hi!
12--2004 00:30 [EMAIL PROTECTED] (Bart Oldeman) wrote to
[EMAIL PROTECTED]:
in kernel.asm. Use std for the memory move: helps if there's overlap
(PCs with a very low amount of RAM).
+fmemcpy(HMADest, HMASource, len);
_Standard_ memcpy() _doesn't_ handles memory overlapping.
Hi!
13--2004 02:06 Arkady V.Belousov wrote to
[EMAIL PROTECTED]:
AVB I test TC MAKE. Not funny image: TC MAKE doesn't support !ifndef,
AVB WMAKED doesn't support $d().
BTW, just for information: TC compiles kernel (from scratch) in 3-4
minutes, BC - 8-9 minutes, OW - 17-25 minutes.
Hello Arkady,
AVB PS4: repeat for my previous question: why to duplicate clean and
AVB clobber? Another one: who make files status.me, *.cod, *.las?
*.cod are generated by MSC, if compiled with 'generate assembly
listing with source' (very handy when debugging)
tom
Hi!
8--2004 09:11 [EMAIL PROTECTED] (tom ehlert) wrote to Arkady V.Belousov
[EMAIL PROTECTED]:
AVB PS4: repeat for my previous question: why to duplicate clean and
AVB clobber? Another one: who make files status.me, *.cod, *.las?
te *.cod are generated by MSC, if compiled with 'generate assembly
On Mon, 5 Apr 2004, Arkady V.Belousov wrote:
PS: config.h also may be removed, because it is dummy (for this only
required to remove reference in globals.h). When (and if!) it will be
required, it may be added back.
config.h contains
struct config { /* Configuration variables */
after
On Mon, 5 Apr 2004 23:13:16 +0100 (BST), Bart Oldeman wrote:
Hi, in the FAQ, somebody claims that file handle 4 should default to
PRN:
http://fd-doc.sourceforge.net/faq/cgi-bin/viewfaq.cgi?faq=incoming/224
Any idea why this would work at all? And why it works in MS but not in
FreeDOS? Used
At least one of your emails was trapped by the SF mail system until I
was able to free it this morning. Emails may not be over 40k in length,
or else they are held until the list owner (me) accepts or rejects them
(a manual process.)
-jh
Arkady V.Belousov wrote:
Hi!
[Don't know what
Hi, in the FAQ, somebody claims that file handle 4 should default to PRN:
http://fd-doc.sourceforge.net/faq/cgi-bin/viewfaq.cgi?faq=incoming/224
Any idea why this would work at all? And why it works in MS but not in
FreeDOS? Used language is C.
Look at the definitions in stdio.h - stdaux is
MS-DOS: CON, AUX, PRN, CLOCK$, A:-D:, COM1, LPT1, LPT2, LPT3, CONFIG$,
COM2, COM3, COM4
FreeDOS: CON, PRN, AUX, LPT1, LPT2, COM1, COM2, COM3, COM4, CLOCK$, A:-D:
Fortunately, fixing this is very easy. It's enough to swap the
corresponding entries in io.asm. Do I need to provide a patch for
Fortunately, fixing this is very easy. It's enough to swap the
corresponding entries in io.asm. Do I need to provide a patch for this?
Here it is, below. Now stdaux and stdprn should work as in MS-DOS.
As always, a patched CVS kernel binary (FAT32, 80386, BC 4.52, aPack) is
available in my
Erwin Veermans schreef:
Forbidden
You don't have permission to access /~lig/romdsk/romd-bin.rar
on this server.
What am I doing wrong, or should I send some cigars first ?
;-)
confirmed.
do you compile from source or always work with binaries like I did?
latest binary from Jeremy took a
Forbidden
You don't have permission to access /~lig/romdsk/romd-bin.rar on
this server.
confirmed.
do you compile from source or always work with binaries like I did?
Usually I work with the official kernel release (binary). But when time
goes by and some interesting patches float
Hi Eric,
Eric Auer escribió:
Hi, in the FAQ, somebody claims that file handle 4 should default to PRN:
In my undersanding, handle 4 is stdprn (the other three being stdin,
stdout, and stdaux, always using C's notation). So it shoulds sensible
that it should point to PRN anyway, isn't it?
Hello Arkady,
AVB I test batch and make files both under OW12 and BC31
would be great if you ewoild test them with TV 2.01 also (this is a
reference compiler, BC31 not)
btw: there is absolutely no need to mess with them - they usually
work.
tom
Arkady V.Belousov schreef:
Hi!
4--2004 17:55 [EMAIL PROTECTED] (tom ehlert) wrote to Arkady V.Belousov
[EMAIL PROTECTED]:
AVB I test batch and make files both under OW12 and BC31
te would be great if you ewoild
ewoild=perform?
would - 'if you would test them'
te test them with TV 2.01
On Mon, 29 Mar 2004 18:55:44 -0300, Alain wrote:
New Power supplies are very cheap. For that they have simplified many
important circuits. They don't handle current fluctuations vary well.
Well, again from bad to worse... They must come with a BIG red sign HLT
forbidden! then :-(
Lucho
On Mon, 29 Mar 2004 19:00:54 -0300, Alain wrote:
INHO and considering that FreeDOS is in C versus all other DOSes being
in ASM
ROM-DOS, our greatest living competitor (not speaking of the venerable
DR-DOS that is still in coma and PC-DOS that must have finally died in
2002) is also written 90%
On Fri, 26 Mar 2004 22:22:20 + (GMT), Bart Oldeman wrote:
Can you check again? I think I solved at least Lucho's problem during the
init phase -- when fnodes could overlap disk buffers! Weird things could
happen indeed.
Congratulations, Bart! Bug fixed indeed - just tried. But I keep thinking
On Sat, 27 Mar 2004, Arkady V.Belousov wrote:
Batch file:
__O\_/_\_/O__
@echo off
ver/r
set a=1
set b=if %%a%%== echo b
set c=if not %%a%%== echo c
%b%
%c%
_
Hi!
27--2004 12:18 [EMAIL PROTECTED] (Bart Oldeman) wrote to
[EMAIL PROTECTED]:
LG Bad news: the new build batch files don't do anything in 4DOS, probably
BO it's picky about
BO call config
BO instead of
BO call config.bat
And? [BTW, just check under freecom - also all works.]
PS: I not
Hi!
27--2004 21:10 [EMAIL PROTECTED] (Bart Oldeman) wrote to
[EMAIL PROTECTED]:
Becuase I show in skipped part you, that this doesn't (always) works.
BO that (not accepting call default.bat) is a bug in 4dos 6.02 then that
call cls.com calls internal command both in NDOS and
Hi!
26--2004 11:24 [EMAIL PROTECTED] (Bart Oldeman) wrote to
[EMAIL PROTECTED]:
Bart, what wrong wit my latest patches for batch files and for sources?
They are small and they are tested - which reason to silently reject them?
BO not rejected, just haven't got around to look at them
On Fri, 26 Mar 2004, Arkady V.Belousov wrote:
Hi!
26-íÁÒ-2004 19:33 [EMAIL PROTECTED] (Bart Oldeman) wrote to
[EMAIL PROTECTED]:
And let me remind you two more bugs, which you don't fix yet: first one
is in INT 21/6C (lost check for nonzero AL)
BO that's not a bug, we discussed
The patched kernel behaves very strangely! :-( It outputs an error
for DEVICE=C:\DOS\HIRAM.EXE line and doesn't load it and repeates
this with many other lines (but not all). For my simpler floppy
configuration, it doesn't load HIMEM64.EXE without even showing an
error!
The
Hi!
26--2004 22:09 [EMAIL PROTECTED] (Bart Oldeman) wrote to
[EMAIL PROTECTED]:
This is bug. When Lucho says that this is patch from me, I quote him my
letter where was _not_ sayed, that check for AL should be removed - there
was discussed only checks for DL.
BO That's a
Hi!
26--2004 21:24 [EMAIL PROTECTED] (Luchezar Georgiev) wrote to
[EMAIL PROTECTED]:
[...] bugs, which you don't fix yet: first one is in INT 21/6C (lost
check for nonzero AL)
LG I already wrote you: This is NOT a bug -
What you wrote to me was: You probably forgot about that. Check for
Hi!
26--2004 23:54 [EMAIL PROTECTED] (Bart Oldeman) wrote to
[EMAIL PROTECTED]:
AVB ; the HMA area is filled with 1eh+3(=sizeof VDISK) = 33 byte dummy data,
AVB ; so nothing will ever be below 0x:0031
AVB begin_hma:
AVB times 10h db 0 ; filler [:0..:10]
AVB
Also, where documented VDISK header (where I may read about this)?
BO It's in the VCPI spec. Available at many places including here:
BO www.dose.se/docs/osdoc/unsorted/ProtectedMode/VCPI.txt
No, there sayed only about signature and showed how to copy word value
from offset 0x1E. :(
On Sat, 27 Mar 2004 03:22:59 +0300 (MSK), Arkady V.Belousov wrote:
PS: Just checked TechHelp: it says nothing about AL, only AH=6C.
Definitely bug in RBIL. :(
MS-DOS technical reference defines AL=0 as reserved
(http://www.clipx.net/ng/dos5/ng1ff99.php). We already discussed this
issue last
The patched kernel behaves very strangely! :-( It outputs an error
for DEVICE=C:\DOS\HIRAM.EXE line and doesn't load it and repeates
this with many other lines (but not all). For my simpler floppy
configuration, it doesn't load HIMEM64.EXE without even showing an
error!
The current
The current nightly-kernel may have reached a new landmark in the
quest for smaller conventinal-memory footprint but it lost ground in
usability and compatibility. My test-machines halt on various
arbitrary points telling me: more than two near fnodes requested at
the same time
ok
The current nightly-kernel may have reached a new landmark in the
quest for smaller conventinal-memory footprint but it lost ground in
usability and compatibility. My test-machines halt on various
arbitrary points telling me: more than two near fnodes requested at
the same time
if files=10 would
On Tue, 23 Mar 2004, Arkady V.Belousov wrote:
Bart, let me remind me %subject% issue: why FD returns nonzero field
for FAT32 in (and only in) current BPB?
most likely because of dsk.c: pbpbarray-bpb_ndirent = 512;
Why that line is there? I don't know. It was already in the first FAT32
Hi!
22--2004 14:47 [EMAIL PROTECTED] (Luchezar Georgiev) wrote to FreeDOS-kernel
[EMAIL PROTECTED]:
if (new_diroff == 65535)
Borland C++ complains here. Change the constant to 65535UL (see patch
below).
Hm, don't see letter with these words.
LG Although Borland says constant is long,
On Mon, 22 Mar 2004, Eric Auer wrote:
Hi, about add_far() pointer normalization: I think it would be
better to normalize earlier. If you have a pointer, you normally
have a pointer to a STRUCTURE. If the end of the structure ends
up with an offset 0x then having the POINTER normalized is
On Mon, 22 Mar 2004, Luchezar Georgiev wrote:
:\elv_3e5.1
I mean i:\elv_3e5.1
Sorry for my typo!
should be fixed now. remove_lfn_entries() calls dir_read with the offset
== -1 which is not possible for normal directories (. and ..) but is
possible for root directories. So the 65535 check
Hi!
22--2004 14:23 [EMAIL PROTECTED] (Bart Oldeman) wrote to
[EMAIL PROTECTED]:
BO add_far is only used at a few select places where we want to have the
BO offset part as low as possible. Nothing to do with structures but
BO everything to do with potentially large file reads, with read chunk,
BO
Bart, unfortunately your very last change (scaling and shortening the
directory entry pointer) introduced a bug! When I start my elvis
editor (a vi clone) and exit it, it can't delete its temporary file
ELV_3E5.1 from my XMSDSK RAM disk where is my temporary directory.
4DOS fails to delete it
Hello Arkady,
AVB Then rename add_far into normalize_ptr and remove misleading.
noone is going to rename functions because you don't like the names.
AVB Also,
AVB I may offer next code to always perform normalization:
It's there for some specific purpose.
AVB (BTW, is protection
AVB from
On Mon, 22 Mar 2004, Luchezar Georgiev wrote:
But what if it was the first entry in the root directory? Then the
new_diroff++ in dir_read() will make it -1!
remove_lfn_entries() checks for fnp-f_diroff == 0. The first entry can't
have any LFN entries connected to it.
Bart
But what if it was the first entry in the root directory? Then the
new_diroff++ in dir_read() will make it -1!
remove_lfn_entries() checks for fnp-f_diroff == 0. The first entry can't
have any LFN entries connected to it.
Of course! I should have seen that. This is so for lfn_dir_read() too.
I
On Mon, 22 Mar 2004, tom ehlert wrote:
AVB (BTW, is protection
AVB from wrapping HMA pointer into IVT by replacing wrapping into start of HMA
AVB worth of code?)
a working kernel is worth a lot of code (even if you don't see the
reason immediately)
HANDS OFF THE KERNEL, please.
in the end
On Thu, 18 Mar 2004 11:14:39 +0200, I wrote:
the redirected output contains two consequtive carriage returns though.
I mean that the output file contains extra CRs only after the r and
q input commands, not where DEBUG does its own output.
Good news - I now saw that this is exactly the same
Hi!
21--2004 17:06 [EMAIL PROTECTED] (Luchezar Georgiev) wrote to
[EMAIL PROTECTED]:
I use both features (F3 and Ins to edit command line) in MS-DOS often.
BTW, they are also available in DEBUG. Isn't this mean, that editing
features built-in into kernel?
LG Yes. They're implemented in
I mean: is this mean, that editing code is/should duplicated in kernel
and command.com?
As far as I know, no. FreeCOM has its own command line editor with history
and auto-competion.
---
This SF.Net email is sponsored by: IBM Linux Tutorials
AVB 1. In kernel present editing code.
yes.
AVB 2. If code presented in command.com, how this affects other programs (say,
AVBDEBUG)?
command.com implements it's own doswedit-style input editor.
it doesn't affect other programs (it's not exported)
tom
I mean: is this mean, that editing code is/should duplicated in kernel
and command.com?
As far as I know, no. FreeCOM has its own command line editor with
history and auto-completion.
But:
1. In kernel present editing code.
2. If code presented in command.com, how this affects other programs
Hi!
21--2004 19:50 [EMAIL PROTECTED] (tom ehlert) wrote to Arkady V.Belousov
[EMAIL PROTECTED]:
I again send not finished sentence. :( I mean:
AVB 1. In kernel present editing code.
te yes.
...then which reason to reimplement this in command.com?
AVB 2. If code presented in
The F3-style command line editing is in the kernel because function 0Ah
(3Fh when reading from standard input) in MS-DOS does it. Period. As to
FreeCOM, it has a better (4DOS-style) command line editing and I don't see
a reason for a separate DOSEDIT. Period. I'll not answer anymore.
On Sun, 21 Mar 2004 23:42:26 + (GMT), Bart Oldeman wrote:
It appears that ^C has to be echoed to stdout. This is easy to test, I'm
using a simple test0a program, see below.
If you (in MSDOS) run test0a foo and press ^C then the ^C ends up in
foo.
Or if I run DEBUG BOZA then type ^C and Q
reason is speedup.
It's faster to read a single 360KB file into RAM and then run from
there, than to keep reading a diskette.
guess you had the bootdisk from prerelease 4, or the one below:
http://fdos.org/ripcord/beta9rc5/fdos1440.img
the real floppy contents is accessible as B:
are you the
it's the CDRcache driver which causes the cdrom disk resets, not SHSUCDX
itself.
option 2 should prevent it from loading, as no XMS driver is loaded.
Bernd
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial
That's strange. Then MS-DOS DEBUG would also leak handles...
the difference is that msdos debug calls int21/ah=26 instead of 55. Here's
a kernel bug inspired by the RBIL comment this function is implemented
using the same code as AH=26h taken too literally...
Reality is that the only things
On Wed, 17 Mar 2004 13:37:07 + (GMT), Bart Oldeman wrote:
It looks like a bug in both DEBUG and the kernel.
What happens is the reference count in the SFT gets too high.
1. open: 1
2. int21/ax=4b: 2
3. int21/ax=55: 3 (this function called by debug)
then:
4. int20: 2
5. int21/ah= 3e: 1
... and
On Wed, 17 Mar 2004, Luchezar Georgiev wrote:
The patch below should fix the ZIP media change not detected bug, *if* my
assumption about ZIP driver setting both DF_FIXED and DF_CHANGELINE is
right. Never hurts to assume that this MAY happen though...
If the ZIP drive has its own device driver
Bart,
Or is it really handled via the BIOS as
drive A: or drive C:?
My PC allows for ZIP to be set as first boot device. IF a disk is in it
during bootup it is seen as C:
-or-
If I use Iomega's DOS level drivers GUEST.EXE program on a bootable
floppy disk in A: AND a disk is in the
On Mon, 15 Mar 2004 22:27:45 +0300 (MSK), Arkady V.Belousov wrote:
a
int 3
g=100
q
Run DEBUGT.DRESULT (where DEBUG is by Paul Vojta, MS-DEBUG doesn't
work under FreeDOS).
This is wrong. MS-DOS 7.10 DEBUG *does* work under FreeDOS 7.10! I've used
it many many times.
Under MS-DOS result file
Arkady,
Jim, please, retest with latest bootfix version (1.3) - now it analyzes
not only default, but also current BPB.
Zip file sent to you.
beta9rc4 is outdated
and definitely should be updated.
Considering comments by Luchezar G, there's something wrong on the server I
got that ISO
Hi!
16--2004 18:32 [EMAIL PROTECTED] (Luchezar Georgiev) wrote to
[EMAIL PROTECTED]:
LG So, when I have time (at the week end probably), I'll try to catch the
LG bug. If Bart has time, he may want to overtake me ;-)
Probably, this is not the last bug. I wait details from Jim Lilly, but
On Tue, 16 Mar 2004 22:01:22 +0300 (MSK), Arkady V.Belousov wrote:
Probably, this is not the last bug.
Last bug?! You know just like every order in the army, every bug is a last
but one ;)
looks like FreeDOS doesn't sense media change (in Zip drive, available
as C:)
This is probably because
On Mon, 15 Mar 2004 13:45:43 +0300 (MSK), Arkady V.Belousov wrote:
So, there was a bug in kernel, which was used previously. This
should be reported for those, who prepare ISO images: beta9rc4 is
outdated and definitely should be updated.
There is something wrong here. The latest official kernel
Hi!
15--2004 12:23 [EMAIL PROTECTED] (Luchezar Georgiev) wrote to
[EMAIL PROTECTED]:
should be reported for those, who prepare ISO images: beta9rc4 is
outdated and definitely should be updated.
LG There is something wrong here. The latest official kernel (build 2033)
LG went out on 31 January.
On Sat, 13 Mar 2004 19:16:00 CST, Jim Lilly wrote:
If I remember correctly, FAT32 volumes must be at least 128 MB in size.
Where might I read up on that info?
Microsoft have stated that the minimum is even 256 MB (in
Luchezar,
In any case, ZIP disks must be formatted with FAT16 and nothing else.
Yep, just had the link to Iomega stating that sent to me.
--
Jim Lilly - Team Z
http://www.zonelabs.com/store/content/company/teamzBios.jsp
Using - Virtual Access(OLR), ZAP 4.5, WinXP Pro w/SP1
Hi!
12--2004 21:08 [EMAIL PROTECTED] (Jim Lilly) wrote to
[EMAIL PROTECTED], Arkady V.Belousov:
JL I tried the only updating the boot sector using FreeDOS' SYS and got;
JL D:\Download\FreeDOSsys X: BOOTONLY
JL FreeDOS System Installer v2.9, Sep 24 2003
JL Processing boot sector...
JL Reading old
Hi!
12--2004 20:02 [EMAIL PROTECTED] (Jim Lilly) wrote to
[EMAIL PROTECTED], Arkady V.Belousov:
This is FAT16, so FAT size here should be 190 sectors.
JL Hmmm, THAT particular disk should have been FAT32or I got confused.
This disk (with such clusters count) can't be FAT32.
Under
Hi!
13--2004 15:44 [EMAIL PROTECTED] (Jim Lilly) wrote to ark:
JL Attached is [misc.zip]
JL File notes from Jim Lilly;
JL RSLT_SR6 - ZIP100, FAT, BOOTFIX results
Looks valid and workable.
JL RSLT_16 - ZIP100, FAT, BOOTFIX results
Looks like there is problems: OS says that FAT
Arkady,
http://makeashorterlink.com/?K379136B7
Should I format my Jaz or Zip disk with FAT32?
Answer
Iomega® does not support nor recommend the use of FAT32 formatting
with Zip® or Jaz® disks.
Warning: Data integrity maybe an issue using FAT32 formatting. Iomega
recommends formatting
Hi!
14--2004 14:33 Arkady V.Belousov wrote to
[EMAIL PROTECTED]:
JL Attached is [misc.zip]
JL File notes from Jim Lilly;
JL RSLT_SR6 - ZIP100, FAT, BOOTFIX results
__O\_/_\_/O__
Checking drive C:
Reading default BPB...
[...]
Volume is a
Arkady,
Which OS you was use for tests?
FreeDOS
Which software you use to prepare
(format) these ZIP diskettes?
WinXP Pro initially, SpinRite for the one ZIP disk.
Also, disk geometry in boot record differs from one, reported by OS.
This is, probably, not very important (in given case),
Arkady,
- v2.9 is outdated (old kernel).
Might be, but it's what's on.
http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/beta
9rc4/fdbootcd.zip
Also note; THAT CD of FreeDOS did NOT 'see' anything but the CDROM Floppy
drivesno ZIP, no HD.
- You can't use SYS
On Sun, 14 Mar 2004 07:55:10 CST, Jim Lilly wrote:
[...] SpinRite which uses FreeDOS incorrectly
'claims' to have successfully formatted such FAT32 ZIP-100 disks.yet
fail to boot. THAT is the focal point of troubles with FreeDOS I'm
having.
SpinRite uses FreeDOS for it's formatting
Luchezar,
FreeDOS formatting tool is FORMAT currently maintained by Eric Auer. Why
don't you try to use FORMAT on your ZIP first?
I would if I could, but FreeDOS doesn't 'see' the ZIP drive, it only sees A:
the CDROM. Therefore FreeDOS won't allow me to do anything to my ZIP drive.
By the
On Sun, 14 Mar 2004 08:32:47 CST, Jim Lilly wrote:
FreeDOS formatting tool is FORMAT currently maintained by Eric Auer.
Why don't you try to use FORMAT on your ZIP first?
I would if I could, but FreeDOS doesn't 'see' the ZIP drive, it only
sees A: the CDROM. Therefore FreeDOS won't allow me to
Luchezar,
Have you tried such a driver in MS-DOS or FreeDOS?
I'll setup a DOS bootdisk as such.
How is such done with a FreeDOS boot floppy?
--
Jim Lilly - Team Z
http://www.zonelabs.com/store/content/company/teamzBios.jsp
Using - Virtual Access(OLR), ZAP 4.5, WinXP Pro
On Sun, 14 Mar 2004 10:15:30 CST, Jim Lilly wrote:
Luchezar,
No need to send me a carbon copy, I'm subscribed here.
Have you tried such a driver in MS-DOS or FreeDOS?
I'll setup a DOS bootdisk as such.
How is such done with a FreeDOS boot floppy?
ODIN is already bootable (see FreeDOS site for
Hi!
14--2004 07:55 [EMAIL PROTECTED] (Jim Lilly) wrote to
[EMAIL PROTECTED], Arkady V.Belousov:
Not needed to CC for me, I subscribed to [EMAIL PROTECTED]
Which OS you was use for tests?
JL FreeDOS
Probably, bug in FreeDOS kernel. I think, Bart may/should clarify this,
may this is
On Sun, 14 Mar 2004 17:42:11 -, James Stockton wrote:
Tell me what to test smile
And another! Not Iomega Zip/Jazz G FAT32 issues were
mentioned. Please say required Kernel, etc.
---
This SF.Net email is sponsored by: IBM Linux
Hi!
14--2004 20:47 Arkady V.Belousov wrote to
[EMAIL PROTECTED]:
AVB Probably, bug in FreeDOS kernel. I think, Bart may/should clarify
AVB this, may this is expected behavior.
---^^^ may be
AVB Do you mean, that
AVB - XP formats to FAT16 and makes bootable: diskette boots
AVB
Whats me choice of kernels smile?
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
On Sun, 14 Mar 2004 20:47:44 +0300 (MSK), Arkady V.Belousov wrote:
Which OS you was use for tests?
FreeDOS
Probably, bug in FreeDOS kernel. I think, Bart may/should clarify this,
maybe this is expected behavior.
What we're talking about here? Does the bootstrap from FreeDOS fail? If
so, it's
Hi!
14--2004 20:47 Arkady V.Belousov wrote to
[EMAIL PROTECTED]:
AVB Probably, bug in FreeDOS kernel.
Ops, sorry, too husty conlusion: BOOTFIX analyzes _default_ BPB, which
is _suggestion_ by OS for given media. Boot record should be compared with
current BPB, which is used by OS for
Luchezar,
You need to make a CONFIG.SYS (device=iomega_driver_name)
Will do.
(Do you mean that IOMEGA still really support DOS??? ;-)
Nothing NEW, but older DOS/Win 3.1 drivers for 'guest' are available in
their archives.
--
Jim Lilly - Team Z
Luchezar,
Does the bootstrap from FreeDOS fail? If
so, it's because of the bad boot sector.
Exactly!
If
so, it's because of the bad boot sector. Does FORMAT under FreeDOS fail?
No!
Undetermined, not No! But I'll check.
--
Jim Lilly - Team Z
Arkady,
Moreover, if MS-FORMAT allows to format 100 Mb as FAT32 (and
XP works with it flawlessly?), then this should be accepted by us also.
But it doesn't work 'flawlessly'. I can read/write/copy/move/delete to -
from a ZIP-100 FAT32 disk, but it is NOT bootable.
Do you mean, that
- XP
Hi!
14--2004 08:32 [EMAIL PROTECTED] (Jim Lilly) wrote to
[EMAIL PROTECTED], Luchezar Georgiev:
FreeDOS formatting tool is FORMAT currently maintained by Eric Auer. Why
don't you try to use FORMAT on your ZIP first?
JL I would if I could, but FreeDOS doesn't 'see' the ZIP drive, it only sees
Arkady,
1. get latest SYS version (comes with kernel, available at freedos.sf.net)
Hmm, when I go to http://freedos.sourceforge.net/ I'm presented with a
bunch of choices. Do you mean for me to get;
kernel 2032?
http://sourceforge.net/forum/forum.php?forum_id=312180
kernel 2033?
Arkady,
But earlier you say, that you test BOOTFIX under FreeDOS and access Zip
as C:?
Probably when I'd used SR, booted off it, then switched diskettes.
I'm beginning to get a bit overwhelmed with all of this. Maybe I'll
tinker around some more tonight, before giving up.
--
Jim
I'm trying out the nightly kernel, not sure if thats what they mean. But its
worth a look i think.
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo
On Sun, 14 Mar 2004 19:42:13 -, James Stockton wrote:
I'm trying out the nightly kernel, not sure if thats what they
mean.
But its worth a look i think.
As soon as I can get to it, will be using
2.0.33
http://prdownloads.sourceforge.net/freedos/ke2033_32.zip?download
Trying to get the
Hi!
14--2004 13:32 [EMAIL PROTECTED] (Jim Lilly) wrote to
[EMAIL PROTECTED]:
1. get latest SYS version (comes with kernel, available at freedos.sf.net)
JL kernel 2033?
Yes. Also, there was some changes in kernel. AFAIK, Luchezar presents
precompiled kernels with all up to date patches
Tested fat32 booting on me hard drive works fine.
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to
901 - 1000 of 1070 matches
Mail list logo
