ntfs4dos booting in Windows ME Dos (Floppy or Cd Image)

[Straight Finger]

Hi all,

I was wondering could anyone point me towards a website where I could
either download or buy/download an (ntfs4dos bootable image) that
could use (Windows ME Dos) rather than FreeDos.

Ideally I am looking for an Ed Jablonowski (www.bootdisk.com) type of
(ntfs4dos boot image) but booting into (Windows Me Dos) rather than
the Freedos of Ed's images.

Even the all critical autoexec.bat & config.sys for loading the
ntfs4dos in (Windows ME Dos) would be welcome

Thank you

[Paul]

Post by Straight Finger
Hi all,
I was wondering could anyone point me towards a website where I could
either download or buy/download an (ntfs4dos bootable image) that
could use (Windows ME Dos) rather than FreeDos.
Ideally I am looking for an Ed Jablonowski (www.bootdisk.com) type of
(ntfs4dos boot image) but booting into (Windows Me Dos) rather than
the Freedos of Ed's images.
Even the all critical autoexec.bat & config.sys for loading the
ntfs4dos in (Windows ME Dos) would be welcome
Thank you

Couldn't you just create a boot disk with ME dos on it then drop the drivers
for ntfs4dos on it? If you copy the config.sys from the freedos disk and
edit as needed.

[Straight Finger]

Couldn't you just create a boot disk withMEdoson it then drop the drivers
for ntfs4dos on it? If you copy the config.sys from the freedos disk and
edit as needed.

Thank you for your helpful reply that seems to be the practical thing
to do.
With that in mind I burned a few of the iso/images that I downloaded
from Ed's site
only to find an unforseen problem namely that despite ntfs4dos firing
up and showing
the ntfs drives that was as far as I could go.

When I tried to access any of the drives that the ntfs4dos driver
displayed I got the following:-
'Volume in drive c has no label'
Neither could I access either the R drive that the ntfs4dos assigned
to the cd or indeed
the lone fat32 drive that I had, despite using the iso that handles
both ide and sata.

I was a bit surprised that the config.sys only contained these
lines:-

rem Disk created by bootdisk.com
files=100
LASTDRIVE=P

While I suppose I should be directing this question now to Ed, I
wanted to acknowledge your reply and pointing out what would seem to
have been the common sense thing to do had the ntfs4dos performed as I
expected.

I notice that while there is great promise and potential associated
with this ntfs4dos driver on lots of websites, there seem to be more
queries than answers about it and i'm beginning to wonder do m/any
people use it for commanl-line-
scanning for which in theory it would seem to be IDEALLY suited.

Thank you for your help

P.

[Paul]

Post by Straight Finger

Couldn't you just create a boot disk withMEdoson it then drop the drivers
for ntfs4dos on it? If you copy the config.sys from the freedos disk and
edit as needed.

Thank you for your helpful reply that seems to be the practical thing
to do.
With that in mind I burned a few of the iso/images that I downloaded
from Ed's site
only to find an unforseen problem namely that despite ntfs4dos firing
up and showing
the ntfs drives that was as far as I could go.
When I tried to access any of the drives that the ntfs4dos driver
displayed I got the following:-
'Volume in drive c has no label'
Neither could I access either the R drive that the ntfs4dos assigned
to the cd or indeed
the lone fat32 drive that I had, despite using the iso that handles
both ide and sata.
I was a bit surprised that the config.sys only contained these
lines:-
rem Disk created by bootdisk.com
files=100
LASTDRIVE=P
While I suppose I should be directing this question now to Ed, I
wanted to acknowledge your reply and pointing out what would seem to
have been the common sense thing to do had the ntfs4dos performed as I
expected.
I notice that while there is great promise and potential associated
with this ntfs4dos driver on lots of websites, there seem to be more
queries than answers about it and i'm beginning to wonder do m/any
people use it for commanl-line-
scanning for which in theory it would seem to be IDEALLY suited.
Thank you for your help
P.

Perhaps the size of the drive are the problem.

Is it essential to mount the drive from dos? Could you not mount it drom
Linux or something? That has NTFS support built in.

[Straight Finger]

Couldn't you just create a boot disk withMEdoson it then drop the drivers
for ntfs4dos on it? If you copy the config.sys from the freedos disk and
edit as needed.

Thank you for your helpful reply that seems to be the practical thing
to do.
With that in mind I burned a few of the iso/images that I downloaded
from Ed's site
only to find an unforseen problem namely that despite ntfs4dos firing
up and showing
the ntfs drives that was as far as I could go.

When I tried to access any of the drives that the ntfs4dos driver
displayed I got the following:-
'Volume in drive c has no label'
Neither could I access either the R drive that the ntfs4dos assigned
to the cd or indeed
the lone fat32 drive that I had, despite using the iso that handles
both ide and sata.

I was a bit surprised that the config.sys only contained these
lines:-

rem Disk created by bootdisk.com
files=100
LASTDRIVE=P

While I suppose I should be directing this question now to Ed, I
wanted to acknowledge your reply and pointing out what would seem to
have been the common sense thing to do had the ntfs4dos performed as I
expected.

I notice that while there is great promise and potential associated
with this ntfs4dos driver on lots of websites, there seem to be more
queries than answers about it and i'm beginning to wonder do m/any
people use it for commanl-line-
scanning for which in theory it would seem to be IDEALLY suited.

Thank you for your help

P.