Is NTFS worth the bother?

O

ozzy

Well I have never yet found a system I couldn't clean of viruses, trojans,
spyware etc. so long as I could boot it and the Recovery Console in XP (boot
it off the XP CD) allows sufficient access to repair a boot problem.

I do agree with Larry about Bart's PE (Preinstalled Environment) boot CD.
It's based on Microsoft's PE which MS will be basing future install versions
of Windows on. Bart's PE is excellent and if you must have an alternate
way to access any system (FAT32 or NTFS) it's the way to go. Larry
referred to the Windows Ultimate Boot CD (WUBCD) site which is based on
Bart's PE. Bart's own site is at: www.nu2.nu/pebuilder
Despite it looking a bit complex, if you follow the instructions it's quite
easy to create the CD and also to add any other favorite utilities you would
like to have on it. There are several versions of Bart's PE now quite
popular although the WUBCD is probably the best. They all provide full
read/write access to NTFS volumes.
Same here, James. I have never had a problem either but we are dealing with a
newbie, Mark, who needs antiviral boot disks now that will allow total access
to the ntfs system. None currently exist.
I use Bart's PE also but it still does not allow avg, f-prot, or norton FULL
direct ntfs access (read/write/delete/execute). This is what Mark needs now. He
has young ones & a BOSS :) that don't want to hear excuses but they want to
hear when ya gonna get it fixed... daddy?

Mark's system is fixed & converted to fat32. He is happy now & can fix his own
future mistakes with AVG boot disks. Mark is learning and no doubt, with time,
he will eventually build up his expertise & knowledge. He may even go back to
NTFS but for now he wants ease & simplicity.

Mark is new to the usenet world & was amazed on the support this group gave
him. I told him "... well that is just ACF for you.... a bunch of nice folk who
love challenges & love to discuss things regarding freeware. A great place to
hang out :)..."
Mark thanks you all for your help. I thank you all.

ozzy
 
L

Larry Sabo

I use Bart's PE also but it still does not allow avg, f-prot, or norton FULL
direct ntfs access (read/write/delete/execute).

It allows all four, the last provided the program on the busted system
is self-sufficient doesn't need the registry on that system. You can
still scan the drive, delete infected files, edit the registry to
remove/fix start-up and other entries, and restore the registry to a
pre-problem state (assuming he has been using System Restore). Having
done that, if the system won't boot, you can always do a repair
install to replace missing/corrupted system files.

However, if the registry is truly hosed, a re-install might be
required (without formatting the drive and losing data) and the
programs re-installed. All the user data should be fine.

However, this is fine for a technician to do, not a novice user. One
can't just boot from a diskette and make life happy again,
unfortunately. Only restoration of a drive image might be that easy,
and I don't think he has been imaging his system, IIRC. Perhaps you
should show him how to do that, for the future.

Cheers,
Larry
 
L

Larry Sabo

The weird thing with his malware'd pc was Bart's PE booted with no grief.
Bart's chkdsk ran with no grief too. Inserted AVG boot disks (built on my pc)
and let it do its thing. Bart's PE warned that AVG was in violation of direct
disk access but I let avg continue anyway. It found nothing & the log files
showed that it missed many files.

It's been a while since I've used the AVG boot disks, so I'm not sure
of just what was being run, in what environment. IIRC, the boot disks
need to be booted and run to unpack various files to a ram drive from
which the program is run in DOS mode, but I could be wrong. In DOS
mode, the program wouldn't be able to see the ntfs files, of course.

BartPE includes a number of A-V scanners and they would have scanned
the problematic hard drive and repaired/deleted indected files. The
WinUBCD includes Mwave which is *far* better than AVG anyway, so it
would be interesting to have run it on the bad drive. I've run it on
my system, just as a test, and it works great.

Anyway, I suspect we are getting way off topic for this group.

Cheers,
Larry
 
J

James

ozzy said:
Same here, James. I have never had a problem either but we are dealing with a
newbie, Mark, who needs antiviral boot disks now that will allow total access
to the ntfs system. None currently exist.
I use Bart's PE also but it still does not allow avg, f-prot, or norton FULL
direct ntfs access (read/write/delete/execute). This is what Mark needs now. He
has young ones & a BOSS :) that don't want to hear excuses but they want to
hear when ya gonna get it fixed... daddy?

I just ran my Bart PE disk and I can't see what access problem you are
having? A standard Bart plugin is McAfee and I ran it with no problem, it
had full disk access and did a 100% disk anti-virus scan. I also ran
Adaware on Bart's PE disk and it did a 100% disk scan. Exactly what disk
access problem are you having (file, folder, registry...)? I don't know
anyone else who has this problem either and I wouldn't like people to read
this thread and think Bart's PE disk does not give full NTFS access. You
need to give me a scenario that demonstrates it so I can understand where
the issue is.

Mark's system is fixed & converted to fat32. He is happy now & can fix his own
future mistakes with AVG boot disks. Mark is learning and no doubt, with time,
he will eventually build up his expertise & knowledge. He may even go back to
NTFS but for now he wants ease & simplicity.

If people are more comfortable with FAT32 that's fine but XP with NTFS is
extremely robust, has much better security features, and there are tools to
work with it. Personally I have had much better success recovering systems
based on NTFS than FAT32. I expect people will have to move on eventually
as disk sizes and system software outgrow FAT32.
 
O

ozzy

It allows all four, the last provided the program on the busted system
is self-sufficient doesn't need the registry on that system. You can
still scan the drive, delete infected files, edit the registry to
remove/fix start-up and other entries, and restore the registry to a
pre-problem state (assuming he has been using System Restore). Having
done that, if the system won't boot, you can always do a repair
install to replace missing/corrupted system files.

The weird thing with his malware'd pc was Bart's PE booted with no grief.
Bart's chkdsk ran with no grief too. Inserted AVG boot disks (built on my pc)
and let it do its thing. Bart's PE warned that AVG was in violation of direct
disk access but I let avg continue anyway. It found nothing & the log files
showed that it missed many files.

I took the drive out & scanned it in my computer through fat32 OS. The same avg
found ALL the malware but I didn't fix them. Returned the drive back to his pc
& repeated the scan. Same problem... missed many ntfs files.
I rebuilt the Bart PE cd again just to be sure... same problem.

I imaged Mark's drive then cleaned it on my system with no glitches. Returned
it to his system & it booted & worked with no grief. I then converted it to
fat32 and he & his family are happy once again.
However, if the registry is truly hosed, a re-install might be
required (without formatting the drive and losing data) and the
programs re-installed. All the user data should be fine.

However, this is fine for a technician to do, not a novice user. One
can't just boot from a diskette and make life happy again,
unfortunately. Only restoration of a drive image might be that easy,
and I don't think he has been imaging his system, IIRC. Perhaps you
should show him how to do that, for the future.
Agreed, Larry, not for the newbie but in time I'm sure that he will get to a
comfortable level.
I gave him a clean imaged cd for him to use if his gets damaged in the future.
I am teaching him how to image & backup using freeware :) but he still likes my
[OT] pqmagic better. He finds it faster & does a more thorough job than the
freeware that is out there. He will learn freeware though cause the BOSS has
spoken & doesn't want him to spend anymore money on the computer :)

ozzy
 
J

James

ozzy said:
Thanks but I already had a BartPE cd made & it is useless too cause it will not
allow direct access to the ntfs system :(

Not true, (see my other post.).

From Bart's PE disk website:

"Goodbye to all the good and bad dos-based NTFS utilities! Now we can boot
from a CD-Rom and have full read/write access to NTFS volumes!"

http://www.nu2.nu/pebuilder/
 
J

JanC

howard schwartz schreef:
We all see version of applications offered separately for 9x and win
2x/XP. This is not only to take advantage of additional NT-based
features!

Most of the time that's because of the ANSI/Unicode difference.
 
L

Larry Sabo

The weird thing with his malware'd pc was Bart's PE booted with no grief.
Bart's chkdsk ran with no grief too. Inserted AVG boot disks (built on my pc)
and let it do its thing. Bart's PE warned that AVG was in violation of direct
disk access but I let avg continue anyway. It found nothing & the log files
showed that it missed many files.

It's been a while since I've used the AVG boot disks, so I'm not sure
of just what was being run, in what environment. IIRC, the boot disks
need to be booted and run to unpack various files to a ram drive from
which the program is run in DOS mode, but I could be wrong. In DOS
mode, the program wouldn't be able to see the ntfs files, of course.

BartPE includes a number of A-V scanners and they would have scanned
the problematic hard drive and repaired/deleted indected files. The
WinUBCD includes Mwave which is *far* better than AVG anyway, so it
would be interesting to have run it on the bad drive. I've run it on
my system, just as a test, and it works great.

Anyway, I suspect we are getting way off topic for this group.

Cheers,
Larry
 
D

Duddits

Often not mentioned are NTFS's inherent downsides: generally slower than FAT,
takes up a lot of disk space to perform its additional functions (e.g.,
auditing), and uses memory of unknown (to me) amounts in connection with
windows to implement its added features.

Small price to pay for data integrity. With todays faster drives (SATA and
general improvement of data read/write/seek in PATA drives)
As a result, I read regularly that 128 megs of ram is actually to little to get optimal performance from an XP,
NTFS system, and that users experience up to a 20% performance degregation
when running the same application, on the same hardware, using win XP/NTFS.

Windows XP automatically reduces functionality with anything less than
256mb of ram. You won't find any XP box sold new by a honest company that
has less than 256mb of RAM. Benchmarks improve considerably with 512mb -
1024mb.

regards

Dud
 
O

ozzy

I just ran my Bart PE disk and I can't see what access problem you are
having? A standard Bart plugin is McAfee and I ran it with no problem, it
had full disk access and did a 100% disk anti-virus scan. I also ran
Adaware on Bart's PE disk and it did a 100% disk scan. Exactly what disk
access problem are you having (file, folder, registry...)? I don't know
anyone else who has this problem either and I wouldn't like people to read
this thread and think Bart's PE disk does not give full NTFS access. You
need to give me a scenario that demonstrates it so I can understand where
the issue is.

I would like to clear up that misunderstanding right now.
I DO use Bart's PE cdrom (http://www.nu2.nu/pebuilder/) and it is AWESOME!
I will, for the record, highly recommend its use :)
Hope this clears up that matter.

I do not use Mcafee/Norton. I use AVG & Adaware SE, both of which are not
integrated with Bart's PE yet but that will change shortly I'm sure.

Mark bought the Compaq Presario with Norton 2004 installed & fully registered &
updated as of 3 or 4 days ago when this mess occured. Perhaps his version was
flawed or the viruses disabled it somehow (not uncommon) but when I ran it
before I fixed his pc, Norton claimed there were no problems. I went online &
did an live update. Still no detected malware. (he had Sasser and other
nasties) I suspected Norton compromised from the viruses hence my use of AVG.

Booting up Bart's PE is no problem. Everything checks out. Chkdsk works great
and all the tools Bart includes work great.

--------------------------------------------
(this next part you should be able to duplicate on your end easily.)
Create an AVG rescue disk set with an updated free version.
After creating them, boot up Bart's PE.
Drop to cmd prompt.
Place AVG disk 1 in a:\ drive & run avg.exe /sos
Insert remaining disks as prompted.
Once AVG actually starts, a warning appears: "An application has attempted to
directly access the hard disk, which cannot be supported. This may cause the
application to function incorrectly. Choose 'Close' to terminate the
application."

This is the problem area that does not occur with fat32 systems nor had Mark
stayed with boot disk utilities :).
-----------------------------------------------

Running AVG from avg rescue floppy is where the full ntfs access is denied.
Bart's PE warns that AVG is trying to use direct disk access & doesn't
recommend allowing it. I do anyway cause at this stage, AVG is only going to
read the files... NOT write/delete them. AVG scan picks up NOTHING.
This lack of finding the malware is NOT Bart's PE fault but the reason why ntfs
is not wanted by Mark's family. Utils they are comfortable with cannot
recognize it :) Mcafee's stinger did not find anything either :)

We will never know if these problems would remain the same had Mark's computer
originally been formatted FAT32 but I will let you know if he has another
malware episode on this computer in the near future :)
If people are more comfortable with FAT32 that's fine but XP with NTFS is
extremely robust, has much better security features, and there are tools to
work with it. Personally I have had much better success recovering systems
based on NTFS than FAT32. I expect people will have to move on eventually
as disk sizes and system software outgrow FAT32.


Most home users & novices don't need the NTFS robust security features nor do
they really know what is happening beneath the OS. NTFS & FAT32 is meaningless
to them :)
I also have no problem recovering system regardless of the drive
geometry/structure.

Everyone following this thread, or tuned in late, must realize that it is not
normally this dragged out to eradicate malware. In this case, Mark wanted to be
shown how to do it with tools that HE was comfortable with.... NOT with what
could be used :)
In Mark's case, though, he needed the 'comfort' of fat32 because so many of the
tools he has used before were 16 bit boot disk variety. He is still not
comfortable with 'cd boot' anything variety tools :blush:( but that will change
with more experience.

ozzy
 
O

ozzy

It's been a while since I've used the AVG boot disks, so I'm not sure
of just what was being run, in what environment. IIRC, the boot disks
need to be booted and run to unpack various files to a ram drive from
which the program is run in DOS mode, but I could be wrong. In DOS
mode, the program wouldn't be able to see the ntfs files, of course.

BartPE includes a number of A-V scanners and they would have scanned
the problematic hard drive and repaired/deleted indected files. The
WinUBCD includes Mwave which is *far* better than AVG anyway, so it
would be interesting to have run it on the bad drive. I've run it on
my system, just as a test, and it works great.

Anyway, I suspect we are getting way off topic for this group.

Yes, I agree, just slightly off topic :) but it did show Mark & his family just
how great ACF & its members are. I know of no other (current :) better
introduction to ACF that would have shown them what ACF is all about :blush:).
Thanks again to all.

ozzy
 
O

ozzy

If I wasn't interested in Linux & freeware utilities I would probably
use NTFS, but that isn't the case. I have WinXP on a 8GB Fat32
partition and I try to keep the content under 4.7GB so that it will fit
on a DVD. It's really a personal preference thing, and every one is
different. Here is an interesting read on the subject of partitions-

http://partition.radified.com/

With the pricelessware sites having multitudes of freeware utilities for either
fat/fat32/ntfs systems.... It doesn't really matter :blush:)

As INspire said; it's your personnal choice.

ozzy
 
J

J. S. Pack

this read access is useless when trying to recover from malware.


read/write/delete/execute access is a MUST !

No problem. See below.
FAT32 has a file size limit of 4 GB, so
if you're into video capture and/or DVD image burning then you will
be unable to do these [easily] with FAT32. NTFS files, on the other
hand, can be ANY size;

I've been doing DL size dvd's for years on fat32 systems. Never once
came across a file that was >4GB. The whole directory structure
totalled > 9GB at times, but that is why dvd shrink & such utils are
used. The actual .vob files were never more than 1GB each in size.

But, you see, many people need files bigger than just DL size. Besides, the
other advantages of NTFS are just overwhelming. I'll never, EVER go back to
FAT32 and sitting in front of my machine waiting for a scandisk to finish
and wondering what got corrupted THIS time!!! NEVER!
This is an excellent topic at an extremely fortunate time :)

It was just a little too late as it turned out, sorry.
I have Mark's new computer in front of me (Compaq Presario S6300NX)
with the factory Win XP Home SP1 installed. NTFS boot partition
(109GB) and a 6GB FAT32 hidden recovery partition.

So far, so good.
The last 2 days of grief that Mark endured will demonstrate why MOST
average home users should not use NTFS unless they want to spend lots
of time restoring/recovering their systems. Losing precious data in
the process is a given with inaccessable ntfs systems :(

Well, but he *could* have spent about 15 minutes total. Knowledge!
Knowledge!

And I hate to think how much data (and programs and OS installations)
people have lost from crashed FAT32 filesystems. Look on any given system
at random and notice those .chk files! Try recovering much out of them,
too.

And the cumulative time people have wasted sitting in front of their desks
waiting for the ol' FAT32 scandisk to finish . . . it must amount to
millions of man-hours :(. With NTFS you can say goodbye to that nonsense,
thank god!

Unless you're just masochistic or love anachronisms, of course.
His computer was randomly rebooting whenever his family tried to
connect to the internet (dial-up). Lsass.exe errors and numerous
others I have seen many times before on clients computers.

Too easy I thought.... get rid of the Trojans and viruses & he'll be
all set. Not as easy as I thought. I was just going to take his
computer home, yank out his hard drive & throw it into my system &
purge the nasty malware.... Done it millions of times before & is the
quickest approach.

It's definitely NOT the quickest approach, which I'll give you below.
TOTALLY unnecessary to disconnect his computer and waste time and effort
taking his computer home and disassembling and reassembling it!

All those millions of times . . . .

But then, do you charge by the hour?
Mark didn't want it done that way. He wanted to be shown properly how
to correct this mistake on their part & PREVENT it from happening
again. He also wanted it cleaned up without buying any new software.
Mark did have a valid point with the desire to be self sufficient &
not dependent on others for assistance (admirable ambition I thought
:)

Instinctively he somehow realizes there MUST be a better way. I'm impressed
with this Mark. Maybe he should think about starting a new career in IT.
Norton AV 2004 & Norton Firewall was installed properly on his
computer & fully updated but it still allowed the malware. Booting to
safe mode w/ command prompt was useless as none of the installed
utilities can run properly in safe mode nor recovery mode for that
matter :(
In safe mode w/ command prompt; AVG & F-prot are also useless with
ntfs also. They don't recognize it either.

The trick is to find a bootdisk util that will allow the user to
safely boot to a command prompt that will still allow FULL access to
the ntfs partition (read, write, delete, execute) such that they may
install OR run a disk-based antivirus utility. None exist.

Please stop spreading misinformation. Of course it does very much exist and
is in use and has a very loyal following.
If anyone
does know of such a beast (NO INSTALL & BOOT-DISK style)

I don't see how the trick can be to find a bootdisk util and then require
it not run BOOT-DISK style! I mean, really!

If the computer won't boot because of malware etc. then of course there's
no way around a bootdisk of some kind. Now, FAT32 addicts absolutely love
clinging to their old DOS boot diskettes, even though their modern DELL
might not have a floppy drive ;).
please post
in this newsgroup. Emails to sysinternals & several other gurus also
resulted in the same answer.... none exist. They said either reformat
or try non- destructive recovery. Neither choices were desired by
Mark.

Good on Mark. What fine common sense. Hope he tells off those idiots at
sysinternals and those would-be gurus.
We ended up going with my original method of swapping out his drive to
my system.

Oh, what a monumental waste of time that was for both of you.
His system is now malware free & no critical data was lost.
NTFS is no longer on his system & fat32 IS faster on his AMD Athalon
2800+.

But then Mark's computer was evidently struck with another kind of malware,
almost as bad as that it replaced, that wiped out his reliable, secure,
highly superior NTFS filesystem and replaced with that FAT32 crap. Even as
we speak, Mark's probably sitting in front of blue screen watching a
scandisk, reading about clusters truncated . . . .

You put that NTFS right back on the way it was, you hear? Some repair guy,
eh? The nerve!

Now you've probably got to do the cluster alignment first, too: see
http://www.aumha.org/a/ntfscvt.htm on how to handle that.

Anyone else have a reliable NO INSTALL method to correct ntfs
corruption due to malware, please post to the group. I am sure we are
all ears :)

Cup your ears, pal. Here it comes, a revelation:

Just get Bart's PE Builder free from http://www.nu2.nu/pebuilder/
and make yourself a boot disk on steriods that gives access to just about
any utility you want, even a web browser, and reads/writes NTFS with ease
in a mini-XP environment. Many plugins are available including for
virus/spyremovers (you can build your own, too) and there's an active forum
for support. Fantastic, really, as far as boot disks go!

It also has network drivers so you can just boot up Bart's on the ailing
computer and run whatever you want on its disk from another machine, like
your notebook for example.

Perfect for running your sys files restore from the backup you previously
made with ERUNT, which don't even need to be on a separate partition or
anything. (Just restoring a registry can sometimes be enough to deal
adequately with malware or at least get your system booted well enough to
run what you need.)

A DOS prompt is just PITIFUL compared to that, pal! And I do mean
PITIFUL!!!

OK, you've been told. Yer welcome.
 
J

J. S. Pack

Windows 2000 and XP usually run on NTFS, being based on NT technology.
I strongly suspect at least some of the compatibility problems with our old and
beloved freeware are connected to software that can not read/write to NTFS.
I may be wrong here:

You are, sorry.
I realize virtually all old software that tries to talk to
the disk directly will run into the inpenetrable `hardware layer interface' or
whatever it is called. If software talks to the (NTFS) disk through the bios, I
suppose the bios can translate, yes?

There's no talking through the BIOS . . . .

In short, any software that can't run w/ NTFS, you don't want.
On the other hand NTFS has a lot of cooporate intended features (security,
etc.) that may not be important to single home users, and probably takes
unknown abouts of resources and ram to keep up.

Single home users just love sitting in front of their screens watching
scandisks go by. Then they love rummaging around in .chk files looking for
whatever was lost, and perhaps restoring their OS or running sfc to get
back their system files destroyed or corruped in a typical FAT32 fiasco.
They all have lots of time for doing all that, too, those home users.
Windows 9x does not run on NTFS, and 2000 and XP do not have a simple
command line OS that can be used in times of trouble.

You REALLY got some research to do. Please stop spreading misinformation.
Overall, are the benefits of NTFS sufficient to offset the old, tried and true
programs, and even OSes and command lines, recovery software, etc.
that freeware folks already know and use?

YES!!! I will NEVER go back to FAT32. NEVER! I hate to think I was once
stuck using it!
 
O

ozzy

It's definitely NOT the quickest approach, which I'll give you below.
TOTALLY unnecessary to disconnect his computer and waste time and effort
taking his computer home and disassembling and reassembling it!

All those millions of times . . . .

But then, do you charge by the hour?

Not applicable in this case :) There were other reasons for taking the pc home
but I left that out due to not being revelant to ntfs discussion.
Please stop spreading misinformation. Of course it does very much exist and
is in use and has a very loyal following.

If you read my previous post on the matter, I mentioned Bart's PE. Mark does
not want to create/use cd utils, nor does his wife. They wanted a boot disk
(AVG, Mcafee, Norton, whatever...) that does one thing & only one thing... it
boots up with a antivirus remover. They also wanted to be able to update the
antivirus disk with ease (hence no no burning) They saw Bart's PE in use and
didn't want to use it. (maybe once they have more experience but not right now)
I don't see how the trick can be to find a bootdisk util and then require
it not run BOOT-DISK style! I mean, really!

see note above. I meant that it can't require an install to the infected hard
drive hence old boot disk style :)
If the computer won't boot because of malware etc. then of course there's
no way around a bootdisk of some kind. Now, FAT32 addicts absolutely love
clinging to their old DOS boot diskettes, even though their modern DELL
might not have a floppy drive ;).

Mark & his wife fell into this category :)
Oh, what a monumental waste of time that was for both of you.

In this case, not really. There were other factors involved too which really
had no bearing on the ntfs discussion. (my email is valid for the full detailed
scenario) but I agree with you there are better ways to handle most malware
situations. Removing drives is a last resort at the best of times.
But then Mark's computer was evidently struck with another kind of malware,
almost as bad as that it replaced, that wiped out his reliable, secure,
highly superior NTFS filesystem and replaced with that FAT32 crap. Even as
we speak, Mark's probably sitting in front of blue screen watching a
scandisk, reading about clusters truncated . . . .

Yes, multitudes of malware & other errors.
You put that NTFS right back on the way it was, you hear? Some repair guy,
eh? The nerve!

yes, dad LOL. Hey, I can lead them to water... but I can't make them drink it.
They will be around again.... asking about ntfs. I am sure of it :)

Just get Bart's PE Builder free from http://www.nu2.nu/pebuilder/
and make yourself a boot disk on steriods that gives access to just about
any utility you want, even a web browser, and reads/writes NTFS with ease
in a mini-XP environment. Many plugins are available including for
virus/spyremovers (you can build your own, too) and there's an active forum
for support. Fantastic, really, as far as boot disks go!

Done long ago, since v3.02 I think, and have upgraded to the latest version.
see my note above.

ozzy
 
J

James

ozzy said:
Booting up Bart's PE is no problem. Everything checks out. Chkdsk works great
and all the tools Bart includes work great.

So if you ran Bart PE OK, why did you not run McAfee from the plugin? That
would have been the obvious thing to do?
Running AVG from avg rescue floppy is where the full ntfs access is denied.
Bart's PE warns that AVG is trying to use direct disk access & doesn't
recommend allowing it.

You are using the version that tries to do a boot sector scan which you
cannot access from XP (FAT32 or NTFS). This would have been required for a
FAT32 system. You need to run AVG from a Bart plugin where, just like all
the other anti-virus programs in an XP environment, it will run perfectly
with full NTFS access to any virus on the partition..
This lack of finding the malware is NOT Bart's PE fault but the reason why ntfs
is not wanted by Mark's family. Utils they are comfortable with cannot
recognize it :)

I think I understand the real problem now, it's Mark, not NTFS:) How did
he ever get past Win 3.1? :)
Mcafee's stinger did not find anything either :)

Stinger only scans for a specific group of viruses, it's unlikely to work
where there is heavy infestation.
Most home users & novices don't need the NTFS robust security features

I didn't actually say NTFS has more robust security features, I said it's
more robust and has better security features. Anyone with NTFS experience
will confirm this and it applies equally to home users / novices as it does
to more experienced users. Hopefully Mark will move on and eventually will
appreciate the improvement it brings to his PC experience.
 
D

den

Hey Guys I'm like a ping pong ball :-(
I want to go back to FAT32 then on the next post I'm staying with
NTFS.

What a great learning tread for somebody like me who *was* very happy
with DOS, FAT16 and then FAT32... ;-) No booting problems... etc.
now? not so sure.

Good discussion ; thanks guys

Den
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads


Top