> A ramdisk is sort of like a virtual hard drive that the installer
> creates in memory. It creates this so there is a mountable drive for
> use during the install process. I believe it boots from this, but I am
> not sure. Someone more expert would know better then me. Sometimes it
> takes a few seconds for this stage to finish. The next step should be
> something like "entering second stage install" or something like that.
> At times it could appear to lock up at that point. Are you not waiting
> long enough or is it really locking up? Windows ME has nothing to do
> with what you are seeing. Wiping your hard drive will not help!
Thanks for the reply and the info. I've already wiped the hard drive - oh
well, I'm sick of windows too.
I do wait a long time, but I know it's locked cause the ligts on the
keyboard all locke up and the system is completely unresponsive. The
longest I've waited is maybe 5 minutes - is it possible it would take
longer?
Thanks,
ERic
>
> David
>
> [EMAIL PROTECTED] wrote:
> >
> > A compressed image or ramdisk or something seems to be
> > causing my computer to lock up during install.
> >
> > I'm trying to set it up to dual boot with Windows ME.
> >
> > It always locks up shortly after:
> >
> > Partition check:
> > hda: hda1 hda2 <hda5>
> > RAMDISK: Compressed image found at block 0
> > Uncompressing....
> >
> > I'm wondering if it may have something to do with ME's system
> > restore thing.
> >
> > If I ran fdisk and wiped my hard drive clean would this solve my
> > problem for sure? Would that get rid of this compressed image or
> > ramdisk or whatever? or is that somewhere that fdisk wont touch?
> >
> > Thanks,
> > Eric
