Just instsalled an image copy of Next step 3.3 on my p3 600,
this is what I get when the boot process is almost at the end.
Tank You in advance for Your Help.
but I suspect that NeXTSTEP is very geometry specific.. so I don't think it'll do that kind of thing nicely...
I just dump'd my data & fresh installed & restored... Tedious sure, but it works!
@vittorio:
NeXTSTEP for white hardware ( intel, x86 ) is very particular. It won't work in most combinations of hardware. This included disks (disk size rather), video cards, sound, network, scsi/ide, etc.
If you search the forums you will find many very helpful threads on this issue (hint: look for ones with many replies)
Finally, the specific error with which you double-posted in this forum, means IIRC that it cannot find the *root* partition to mount it. Possibly tweaking your boot arguments/parameters will make that work.
First of all, tanks very much for Your help...
Second, sorry for double posting, Just removed the other one...
The PC I'm installing the image of nextstep, was already installed
and fully working NEXTSTEP 3.3, But because of a power supply fault,
the PC had a crash and lost some file, because now it is
starting without file manager.
All I have at the moment is a dos disk to stat up the system, a program
called Gost, and a cd called NextStep 3.3 basic Image. So I stated the pc, ran Gost, and told it to restore the file image. At the end rebooted the pc and got the alarm I posted. if this can help You to anderstand better the problem, I have another pc "pentium 133" with Next installed and working, with a similar configuration, and I noticed that when it starts is firstly loading the scsi driver. This is not happening in the "p3 600". I've
also tried to move the hard drive from the p133 to the p3 600, and I got panic problem as well.
Vittorio
Sorry I forgot to tell You that in my PC is present an 8G SCSI HD.
And I noticed that is not partitioned to 2 GB, can this be the problem?
But I think it was the same before...
Vitt
personally I think the best way to move around disks is to re-install, re-patch & restore dump files...
Quote from: "neozeed"personally I think the best way to move around disks is to re-install, re-patch & restore dump files...
Do You mean Should I find and installation CD of NextStep ?
Quote from: "vittorio"Quote from: "neozeed"personally I think the best way to move around disks is to re-install, re-patch & restore dump files...
Do You mean Should I find and installation CD of NextStep ?
Yeah, I scored about 4 copies of 3.2 & 1 of 3.3 on eBay... If you know where to uh... 'search' you can find it online.. Dev tools & all that too.
But I wouldn't condone such a thing, but you know you could try booting the original, and adding a second disk doing the dump restore locally. I know that works find on a NeXT I'm unsure on the white pc's though.
Quote from: "neozeed"Quote from: "vittorio"Quote from: "neozeed"personally I think the best way to move around disks is to re-install, re-patch & restore dump files...
Do You mean Should I find and installation CD of NextStep ?
Yeah, I scored about 4 copies of 3.2 & 1 of 3.3 on eBay....
I've already tried to browse e-bay, the only one I've found is from "Blakholeinc". And they dont ship out of USA, I'm actually in belgium...
vittorio,
when you *swap* drives and get a panic (I forget your details right now, so I'm speaking generally) upon booting it's most likely one thing:
It cannot find the root partition/slice.
To get around that you need to change a couple of things: the boot paramemters ( bsd(x,x,x) root=.... or rootdev=... I forget right now ) and the file /etc/fstab
Two ways to change /etc/fstab:
1) edit it before you move the hard drive over
or
2) boot in single-user mode (using the root= or rootdev= parameter and then if you have an editor (pico exists in black NeXTSTEP 3.3, and vi should too), you can edit /etc/fstab and reboot
Search the forums for a more complete set of informations as I'm not about to retype all that stuff.
Also, a *crude* way to duplicate a drive, and I mean *crude* is simply doing the following in Linux (and something similar in Mac OS X):
dd if=/dev/sda of=/dev/sdb bs=16k
sda = your *source* drive
sdb = your *destination* drive (EVERYTHING ON IT WILL BE WIPED AWAY - BEWARE)
Then assuming the *order* of the drives in both systems is the same (so if your NeXT drive was sd0a on machine 1, and then you plug it on machine 2 and it has no other SCSI devices before this drive, it will also be sd0a ), the drive should boot right up.
The *right* way to duplicate a drive is mentioned in the forums, so search around or follow neozeed's method.
Good luck!