[Gllug] NTFS RW

[Stephen Harker]

On Fri, 17 May 2002, Dave Jones wrote:

> On Thu, May 16, 2002 at 11:19:48PM +0100, Stephen Harker wrote:
>  > You're damn right. It COMPLETELY shafted beyond recognition the NTFS 
>  > partition I was trying to 'FIX'. DO NOT USE LINUX NTFS IN READ/WRITE MODE!
>  > I repeat. DO NOT etc...
> 
> Probably not what you want to hear, but.. Well, you were warned 8-)
> 
>  > Bollocks! So anyway, there goes that database.... gurgle gurgle. Piss on 
>  > Bill Gates and all he stands for!! And piss on the person who wrote that 
>  > NTFS code.
> 
> That's probably a little harsh. The work done there was by no means
> to be underestimated. Reverse engineering an on disk format (a
> particularly complicated one at that) is quite a task. It's surprising
> it got as far as it did. Now that the rewritten read-only driver is
> merged in 2.5, work is starting again I believe on write-support.
> Given whats been learned since the first implementation, I'd say there's
> a much better chance of improved NTFS support in the future.
> 
>  >  GRRRRRRR. I saw the signs and I read the warnings and I still 
>  > tried it so I only have myself to blame.
>  > MMmmmm. Beer is good.
> 
> *chuckle* You did have backups right ? Oh well, Beer sounds like
> the best alternative then 8-)
Well normally, I would have but in this instance. Look, do you want the 
whole sorry saga? Well here it is anyway...
I have a Win2k/MSSQL/whatever server which we (as a company) are trying 
out a new database frontend booking engine / saviour of the planet / fix 
all the problems in the company sort of solution (I work for a travel 
company). But it sits there doing sod all most of the time (except SETI 
units) so I thought I would bung in an old sound card I found lying about 
the place, which I did but it turns out to have some obscure TRIDENT dsp 
chip on it and TRIDENT never actually made a win2k driver before they 
decided they weren't going to make sound chips anymore and pulled all 
support. So I found a driver for a chipset that was "almost" the same in 
the hope that it would work but of course it didn't and blue-screened the 
server and rendered it completely un-bootable and blue-screen-aroony 
etc...
So I thought, I'll just bung the drive in my linux box, mount the drive, 
delete the offending \winnt\system32\drivers\blahblah.sys file and hey 
presto. Completely F%$&(&%$*"()$*&ED the whole thing. Plus I cut my finger 
open on the bloody buggery thing when I was getting the drive in and out. 
So today was a complete disaster and I am now quite pissed and probably 
shouldn't be posting. Drinking and dialling again...
Steve
PS Bollocks
PPS I apologise for the coarse language in my posts today. Normal service 
will resume at the first available opportunity.

-- 
Stephen Harker
steve at pauken.co.uk



-- 
Gllug mailing list  -  Gllug at linux.co.uk
http://list.ftech.net/mailman/listinfo/gllug