HowToFixComputers.com




Watched TopicsWatched Topics SearchSearch RegisterRegister Log in to check your private messagesLog in to check your private messages ProfileProfile Log inLog in
Packet Writing in Windows Vista!

 
Post new topic   Reply to topic    Index -> CD Recordables
Author Message
Gerry_uk
Guest





PostPosted: Thu Apr 26, 2007 4:12 pm    Post subject: Packet Writing in Windows Vista! Reply with quote

Hi,

Packet writing is where your CD or DVD drive gets a drive letter and you
can read/write files just like any other hard drive, thumb drive etc.

I've done extensive testing of UDF packet writing in Vista. It doesn't
require additional software such as Direct CD or InCD.

I've tested CD-RW and DVD-RAM from Windows 2000 (InCD) for Interop to
Vista and also going back the other way.

One thing to look out for, Vista will format to UDF 2.01, so if you want
R/W capability it's best to format all your CD-RW media to minimum 2.01,
the default for many years was UDF 1.5, DVD-RAM will usually be UDF 2.5
by default, so not an issue.

After a lot of testing, the DVD-RAM is the ultimate for RW packet
writing, a joy to use. It's pre-formatted so you can just take it out of
it's box and start writing straight away. Many new television PVR
recorders also support DVD-RAM.

If your burner doesn't have DVD-RAM, you bought the wrong burner, but
DVD-RW has almost the same capabilities for DVD packet writing.

Interestingly, they chose NOT to support MRW.

The drives I've used in these tests are Plextor PX750A. I've tested four
on four different computers, two with Win2k, two with Vista.

--
Gerry_uk
Back to top
Fix your Windows Problems - FAST.
FREE Safe Scan Registry Check. Locate & Fix Errors in Minutes!
Jon
Guest





PostPosted: Sat Apr 28, 2007 1:04 pm    Post subject: Re: Packet Writing in Windows Vista! Reply with quote

"Gerry_uk" <gerry666uk@yahoo.com> wrote in message
news:1177603302.2678.0@proxy02.news.clara.net...
Quote:
Hi,

Packet writing is where your CD or DVD drive gets a drive letter and you
can read/write files just like any other hard drive, thumb drive etc.

I've done extensive testing of UDF packet writing in Vista. It doesn't
require additional software such as Direct CD or InCD.

I've tested CD-RW and DVD-RAM from Windows 2000 (InCD) for Interop to
Vista and also going back the other way.

One thing to look out for, Vista will format to UDF 2.01, so if you want
R/W capability it's best to format all your CD-RW media to minimum 2.01,
the default for many years was UDF 1.5, DVD-RAM will usually be UDF 2.5 by
default, so not an issue.

After a lot of testing, the DVD-RAM is the ultimate for RW packet writing,
a joy to use. It's pre-formatted so you can just take it out of it's box
and start writing straight away. Many new television PVR recorders also
support DVD-RAM.

If your burner doesn't have DVD-RAM, you bought the wrong burner, but
DVD-RW has almost the same capabilities for DVD packet writing.

Interestingly, they chose NOT to support MRW.

The drives I've used in these tests are Plextor PX750A. I've tested four
on four different computers, two with Win2k, two with Vista.

--
Gerry_uk

Thanks Gerry. Your test results and report will prevent a lot of grief for
those interested in packet writing on W2K and Vista.
Back to top
Marlin Singer
Guest





PostPosted: Sun Apr 29, 2007 12:38 am    Post subject: Re: Packet Writing in Windows Vista! Reply with quote

Jon wrote:
Quote:
"Gerry_uk" <gerry666uk@yahoo.com> wrote in message
news:1177603302.2678.0@proxy02.news.clara.net...
Hi,

Packet writing is where your CD or DVD drive gets a drive letter and you
can read/write files just like any other hard drive, thumb drive etc.

I've done extensive testing of UDF packet writing in Vista. It doesn't
require additional software such as Direct CD or InCD.

I've tested CD-RW and DVD-RAM from Windows 2000 (InCD) for Interop to
Vista and also going back the other way.

One thing to look out for, Vista will format to UDF 2.01, so if you want
R/W capability it's best to format all your CD-RW media to minimum 2.01,
the default for many years was UDF 1.5, DVD-RAM will usually be UDF 2.5 by
default, so not an issue.

After a lot of testing, the DVD-RAM is the ultimate for RW packet writing,
a joy to use. It's pre-formatted so you can just take it out of it's box
and start writing straight away. Many new television PVR recorders also
support DVD-RAM.

If your burner doesn't have DVD-RAM, you bought the wrong burner, but
DVD-RW has almost the same capabilities for DVD packet writing.

Interestingly, they chose NOT to support MRW.

The drives I've used in these tests are Plextor PX750A. I've tested four
on four different computers, two with Win2k, two with Vista.

--
Gerry_uk

Thanks Gerry. Your test results and report will prevent a lot of grief for
those interested in packet writing on W2K and Vista.


Only problem is, packet writing and RW discs of any kind are far more

likely to lose that data than keep it. If you are trying to use this for
saving data, one day you will be in for an unwanted surprise.
Back to top
Gerry_uk
Guest





PostPosted: Wed May 02, 2007 1:28 am    Post subject: Re: Mike Richter's Cockamamie Mumbo Jumbo on Packet Writing Reply with quote

Hi smh,

Quote:
"Live UDF" of Vista supports read/write UDF 1.02, 1.50, 2.01, 2.5. The
*default* UDF version on CD/DVD is 2.01. You can format in UDF 1.50 for
compatibility with older packet writing softwares.

This is correct, no problems reading UDF 1.50, however I ran into some
problems trying to write to an InCD formatted UDF 1.50 CD-RW under
Vista. I found using 2.01 to be reliable. It's well worth the move to
2.01 anyway, some operations are faster.

Quote:
Live UDF slow and buggy
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1062864&SiteID=1

I find for CD-RW, it works well on 2.01 (haven't tried 2.5), but I've
moved everything to DVD-RAM now, and it's certainly not slow or buggy.

--
Gerry_uk
Back to top
Gerry_uk
Guest





PostPosted: Thu May 03, 2007 1:15 am    Post subject: Re: Mike Richter & "Lethal for archiving" Reply with quote

Hi smh,

Quote:
One sync program I used had some problem with InCD's "Non-Allocatable
Space". Doesn't Live UDF have a special file like that?

I know about the "Non-Allocatable list" or what ever it's called, but
I've never had any problems with it. I just use the basic WinAPI calls.

One thing that's crazy with InCD is that if you use a synch program,
that synch program will have to "access" each file, in order to see if
it needs updated, BUT merely "accessing" the file causes the "last
accessed" date/time stamp to be updated! This causes a serious
performance problem. I wrote to Ahead about it, and got a reply
something like "we value you custom".

Under DirectCD, the Adaptec engineers had spotted this problem and their
software didn't try to change the "last accessed" date/time stamp, clever!

With InCD, sometimes just looking at a file, or hovering the mouse over
it, causes the drive to burst into activity and start writing, for
reasons explained above.

--
Gerry_uk
Back to top
Gerry_uk
Guest





PostPosted: Sat May 05, 2007 2:26 am    Post subject: Re: Mike Richter's Cockamamie Mumbo Jumbo on Packet Writing Reply with quote

Hi smh,

Quote:
In order to be called DVD-RAM drive, the defect management is performed
by the drive. Bear in mind that the "defect management" is nothing more
than verify the write and then relocate the faulty block data to the
spare area, be it done in software or hardware. (In that perspective,
hardware management is nothing more than putting the software in
firmware.) Also, the defect management does not build any sort of
recovery record.

OK, that explains a lot!

Quote:
RAMPRG - RAM Promotion Group:
http://www.ramprg.com/en/a/main.html

This looks interesting, but it wants Flash plug-in, is there a text-only
version?

--
Gerry_uk
Back to top
Gerry_uk
Guest





PostPosted: Sat May 05, 2007 2:26 am    Post subject: Re: Mike Richter & "Lethal for archiving" Reply with quote

Hi smh,

The post from "Marc" is not related to what I'm talking about. He's
talking about when the files get burned with a time stamp that is the
time the file was written to disk, instead of the original time on the
source media.

Quote:
it needs updated, BUT merely "accessing" the file causes the "last
accessed" date/time stamp to be updated! This causes a serious
performance problem.

Whatever operation you are performing, you should not go by the accessed
time. You should go by the modified time.

I know, obviously I don't use this time-stamp. See below..

Quote:
And don't understand how
changes in the accessed time affect "performance".

OK, here's how it works. Windows has at least two time stamps,
LastModified, LastAccessed. The only one we care about is LastModified
_but_ when ever you "look" at a file in Windows the LastAccessed stamp
gets updated to reflect the time you "last accessed" the file.

On a fixed disk volume, this is not an issue because it's very fast and
is cached anyway. On a CD-RW it's a problem. Let's say you insert your
packet writable CD-RW into a Windows computer and look at 400 photos
(e.g. using a Thumbs Viewer program), Every file read by the photo
viewing program will suddenly cause a WRITE operation on the CD-RW
drive, causing the laser to fire-up. Bad, bad, bad. You only performed
READ operations on the disk, but you ended up doing 400 write operations
and that's bad for performance (reading and writing at the same time).

Quote:
Under DirectCD, the Adaptec engineers had spotted this problem and their
software didn't try to change the "last accessed" date/time stamp, clever!

--
Gerry_uk
Back to top
Gerry_uk
Guest





PostPosted: Sat May 05, 2007 9:26 pm    Post subject: Re: Mike Richter & "Lethal for archiving" Reply with quote

Hi smh,

The writing of the LastAccessed timestamp is not done in "idle" time, it
starts as soon as you perform file read operations on the disk. Updating
accessed time on removable media is pointless, it's not a "bug" to turn
off this behavior, it's a good idea! Actually, the LastAccessed time is
pointless even on fixed disks; as soon as an Audit guy tries to look at
the timestamp, it will suddenly be updated because _he_ has just tried
to look at it.

smh wrote:
Quote:
. --------------------------------------
Mike Richter, were you born with
"Scam Artist" emblazoned on your face?
--------------------------------------

Gerry_uk wrote:
Hi smh,

The post from "Marc" is not related to what I'm talking about. He's
talking about when the files get burned with a time stamp that is the
time the file was written to disk, instead of the original time on the
source media.

(There is no time stamp called "original".)

You are correct that "Marc" - in fact all three posts - is not talking
about the unimportant accessed time, but about the all important
modified time -- which should not be changed to that of creation/copy
time.

it needs updated, BUT merely "accessing" the file causes the "last
accessed" date/time stamp to be updated! This causes a serious
performance problem.
Whatever operation you are performing, you should not go by the accessed
time. You should go by the modified time.
I know, obviously I don't use this time-stamp. See below..

And don't understand how
changes in the accessed time affect "performance".
OK, here's how it works. Windows has at least two time stamps,
LastModified, LastAccessed.

Whatever happened to the "original" time?

The only one we care about is LastModified

Wouldn't have known that's the case when you sort of discredit the
Marc's post because it does not talk about the accessed time you are
harping about.

_but_ when ever you "look" at a file in Windows the LastAccessed stamp
gets updated to reflect the time you "last accessed" the file.

On a fixed disk volume, this is not an issue because it's very fast and
is cached anyway. On a CD-RW it's a problem. Let's say you insert your
packet writable CD-RW into a Windows computer and look at 400 photos
(e.g. using a Thumbs Viewer program), Every file read by the photo
viewing program will suddenly cause a WRITE operation on the CD-RW
drive, causing the laser to fire-up. Bad, bad, bad. You only performed
READ operations on the disk, but you ended up doing 400 write operations
and that's bad for performance (reading and writing at the same time).

Those write operations are done in idle period so as not to interfere
with any pending operation.

Under DirectCD, the Adaptec engineers had spotted this problem and their
software didn't try to change the "last accessed" date/time stamp, clever!

You access a file, but the access time is not changed. And you call that
"clever". I call it a bug.


--
Gerry_uk
Back to top
Display posts from previous:   
Post new topic   Reply to topic    Index -> CD Recordables All times are GMT
Page 1 of 1

 

 MemberlistMemberlist  UsergroupsUsergroups



Powered by p|-|pBB

Featured Sites: DIY Projects