[9fans] r4 issues (one resolved! yay! one new)

[9fans] r4 issues (one resolved! yay! one new)

[Don]

1 down! 2 to go :)
Russ' emailed me with the following:
> 	for(i in sdC0 sdC1 sdD0 sdD1)
>		echo -n dma >/dev/$i/ctl
This improves audio quality greatly. Thanks,
Russ. No more chops :)

cdfs, though, isn't working with my writable
cdrom drive. I have a Plextor PX-W1210A1.07
if that helps. From the man page I am reading
that new speed controls exist in cdfs.
Apparently the numeric equates to kilobytes
per second. Am I misunderstanding? I am
going to assume that cdfs misinterprets the
cdrom's speeds. According to ctl read I get
"maxspeed read 5645 write 2117" though the specs
say speed is write@12kbps/10kbps read@32.
I'm also going to assert that this causes the
buffer underrun since cdfs writes too slow
for the cdwriter. How would one go about fixing
this?

On to new things. This is just a weird occurance
in /dev. Try:
	cd /dev/sdC0/ && cd ..
	lc
Do you only see sd entries?
Now right afterwards, try:
	cd ../ && cd dev
Do you get "Can't cd dev: 'dev' file does not exist"?
I do.

webfs has some breaks when cat'ing files..
hi

I'm really enjoying '4e' btw. Its alot of fun even with
the video probs. I just figure out ways around it until
someone patches it.
Don

[9fans] Re: r4 issues (one resolved! yay! one new)

[Casey Webster]

"Don" <north_@www.7f.no-ip.com> wrote in message
news:8f6cf824.0204300134.17db2629@posting.google.com...
 According to ctl read I get
> "maxspeed read 5645 write 2117" though the specs
> say speed is write@12kbps/10kbps read@32.

for cd speeds, 1x == 150kbyte/sec, and any other speed
is a multiple of that.  I imagine you meant write 12x/10x,
read 32x, which translates to: write: 1.8MB/s / 1.5MB/s,
read: 4.8 MB/s

[9fans] Re: r4 issues (one resolved! yay! one new)

[Don]

> for cd speeds, 1x == 150kbyte/sec, and any other speed
> is a multiple of that.  I imagine you meant write 12x/10x,
> read 32x, which translates to: write: 1.8MB/s / 1.5MB/s,
> read: 4.8 MB/s
Ahhh, now I get it. The cdwriter was overclocked so it was
probably wrapping around to an incredibly slow speed or
somethin. Now that I adjust the speed to the proper setting
(12 * 150) it writes with no errors what-so-ever. Nice.
Thanks for setting me straight, Casey.
Don