Pixel a �crit :
> 
> bruno <[EMAIL PROTECTED]> writes:
> 
> [...]
> > ok suppose I can re-create this situation
> > 1 what kind info (log files, dumps etc.. ) would you need to isolate the
> > problem ?
> 
> well, why is windows not happy!
> 
you're asking ?
I guess because an innocent fat32 partition was killed by a bad Linux
prog ;-)
I said innocent because nobody ever asked mandrake install to do
anything to this disk drive which was fully dedicated to windows
Do you realise this is like... a murder or should I say... a genocid
because millions of innocent bytes who were living on this partition are
now dead :-(
I  tried to find who what was the reason for this war  and if anyone
still survive there, but after this blood bath :

1-Mr Microsoft Scandisk refused to tell anything and prefered to die
2-Mr Linux Fdisk refused to display anything about an "invalid"
partition
3-Mr Mandrake Diskdrake displayed me a nice blue graphic showing the
partition but refused to do anything on it

Fortunatly Mr Linux Hexedit/dev/hdb and Mr Windows Fdisk accepted to
burry everybody on hdb and recreate an empty :-(( fat32 

But really in this story that was not Mr M$ Windows who was not happy (
no sentiment anyway ) guess who was not happy ?? a silly guy called
bruno who had to reload tons of data and wasted a lot of time for that
...
BTW I wonder how many silly guys like me on this planet still have a
standard DELL computer with a Western digital 3,4 go disk drive ?? 
Would these guys try one day this fancy graphical install of linux where
you just have to click and watch and..... wait ;-)
 ?? Who knows ...

> > 2 during the  install in expert mode is there some tool I can use to
> > help debugging the problem ??
> 
> the report.bug, to get it:
> 
> switch to console 2
> put a fat floppy in floppy drive
> and type "bug"
> 

ok but when ?? just after diskdrake wrote the partition table ?? do I
have to tail -f /root/ddebug.log to determine when to do it ?
as I already told you diskdrake didn't display any special message,
everything looked fine when the problem occured.

> -> it will put report.bug on floppy  and this file interests me :)
> 
> thanks, cu Pixel.
sans rancune :-)
Bruno

Reply via email to