Title: Cube fails to boot, even on a clean install
Post by: pentium on September 16, 2008, 12:48:00 AM
Post by: pentium on September 16, 2008, 12:48:00 AM
Well now that I have a floppy drive I set out to install NeXTSTEP 3.3 on my cube.
The install went well and then I installed the developer packages and then shut the system off for the afternoon.
Then when I came back to the system and turned it on, I got this:
Odd. :/
Well I thought I biffed the install so I did it again and as soon as I finished the main install (as In it rebooted on it's own twice during the install and then finally shows me the desktop)I shut the system off and then back on again and got the same no boot issue again.
What is it? Is NeXTSTEP not installing properly or has it something to do with the address my hard drive is on?
The install went well and then I installed the developer packages and then shut the system off for the afternoon.
Then when I came back to the system and turned it on, I got this:
Odd. :/
Well I thought I biffed the install so I did it again and as soon as I finished the main install (as In it rebooted on it's own twice during the install and then finally shows me the desktop)I shut the system off and then back on again and got the same no boot issue again.
What is it? Is NeXTSTEP not installing properly or has it something to do with the address my hard drive is on?
Title: Cube fails to boot, even on a clean install
Post by: Jenne on September 16, 2008, 02:43:17 AM
Post by: Jenne on September 16, 2008, 02:43:17 AM
I remember my cube having te same problems when using HD's ID set to "0" - it didn't matter if IBM, Seagate or whatever. Although it still does make no sense to me only changing the ID from "0" to "1" solved the problems.
BUT:
If Your HD is the original one once paced into that cube with ID "0" it doesn't make even any senso to m anymore. Sorry, I know this isn't very helpfull and I know what hassle it is to unmount a cube...
J
BUT:
If Your HD is the original one once paced into that cube with ID "0" it doesn't make even any senso to m anymore. Sorry, I know this isn't very helpfull and I know what hassle it is to unmount a cube...
J
Title: Cube fails to boot, even on a clean install
Post by: pentium on September 16, 2008, 02:59:35 AM
Post by: pentium on September 16, 2008, 02:59:35 AM
Nah, it's a 2Gb Seagate. The old Maxtor crashed a long time ago (though it still works well to keep my bedroom door chocked open).
I'll have to disassemble the thing and change the scsi ID tomorrow after I get back from school.
I'll have to disassemble the thing and change the scsi ID tomorrow after I get back from school.
Title: Cube fails to boot, even on a clean install
Post by: pentium on September 16, 2008, 04:54:16 PM
Post by: pentium on September 16, 2008, 04:54:16 PM
Well I added a jumper to the drive and switched the ID from 0 to 1 and then tried again and got the same error.
Hmmm, would reinstalling everything again fix it? Just want to know because it takes a good hour to just install NeXTSTEP 3.3.
EDIT: One other thing.
what is the proper boot command for booting from a scsi disk on ID 1?
I currently have it set as "sd 1,0" and I don't think that is correct.
Hmmm, would reinstalling everything again fix it? Just want to know because it takes a good hour to just install NeXTSTEP 3.3.
EDIT: One other thing.
what is the proper boot command for booting from a scsi disk on ID 1?
I currently have it set as "sd 1,0" and I don't think that is correct.
Title: Cube fails to boot, even on a clean install
Post by: un on September 16, 2008, 07:35:38 PM
Post by: un on September 16, 2008, 07:35:38 PM
what's the jumper setup on the seagate drive? I had to fiddle with the other jumpers to get my NeXTStation to recognise the drive I got for it.
Title: Cube fails to boot, even on a clean install
Post by: helf on September 16, 2008, 08:25:12 PM
Post by: helf on September 16, 2008, 08:25:12 PM
i had to either enable or disable parity on my seagate drive to get my slab to see it. i forget which setting it was :P
Title: Cube fails to boot, even on a clean install
Post by: pentium on September 16, 2008, 08:37:40 PM
Post by: pentium on September 16, 2008, 08:37:40 PM
Well it seems to be happy now that I set the ID to 1 and reinstalled NeXTSTEP.
Now the next task is to get the box to talk to my Windows 2000 server in the basement so I can load the system with patches and a few archived programs.
I also might need to figure out why out of a 2.1Gb drive, only 1Gb was properly partitioned. I assume this is that 2Gb partition limitation kicking in, right? if so, how can I get access to the other 1Gb? fstab?
EDIT: Also, configure.app seems to be broken. :/
Now the next task is to get the box to talk to my Windows 2000 server in the basement so I can load the system with patches and a few archived programs.
I also might need to figure out why out of a 2.1Gb drive, only 1Gb was properly partitioned. I assume this is that 2Gb partition limitation kicking in, right? if so, how can I get access to the other 1Gb? fstab?
EDIT: Also, configure.app seems to be broken. :/
Title: Cube fails to boot, even on a clean install
Post by: cubist on September 16, 2008, 10:25:55 PM
Post by: cubist on September 16, 2008, 10:25:55 PM
Quote from: "pentium"EDIT: Also, configure.app seems to be broken. :/
Configure.app is only for Intel. (Sparc and PA I don't know...)
Title: Cube fails to boot, even on a clean install
Post by: pentium on September 16, 2008, 10:40:48 PM
Post by: pentium on September 16, 2008, 10:40:48 PM
Quote from: "cubist"Then why did it install on my NeXT system?Quote from: "pentium"EDIT: Also, configure.app seems to be broken. :/
Configure.app is only for Intel. (Sparc and PA I don't know...)
Title: Cube fails to boot, even on a clean install
Post by: Jenne on September 16, 2008, 11:30:26 PM
Post by: Jenne on September 16, 2008, 11:30:26 PM
I don't know, why it installs, too. But many apps seem to be broken after installing them. Open the preferences app and go to "UNIX" on the furthermost rigt, turn on expert. Close preferences app.
Click on the app file that seems to be broken and fix the rights by using the inspector from the menu. It's like assigning FTP rights, sometimes a "777" will do the job, to be more exact: mark every field in the file properties window, close that window and you will sometimes notice that the "broken" file's icon will change.
Does not work every time, I noticed...
J
Click on the app file that seems to be broken and fix the rights by using the inspector from the menu. It's like assigning FTP rights, sometimes a "777" will do the job, to be more exact: mark every field in the file properties window, close that window and you will sometimes notice that the "broken" file's icon will change.
Does not work every time, I noticed...
J
Title: Cube fails to boot, even on a clean install
Post by: cubist on September 17, 2008, 12:10:30 AM
Post by: cubist on September 17, 2008, 12:10:30 AM
Quote from: "pentium"Then why did it install on my NeXT system?Always does. Wasn't worth the bother of special installation and/or something that could be moved to an NFS'd disk for common usage. Who knows. (I believe there's an Easter Egg in it, however, for Intel people.)
Title: Cube fails to boot, even on a clean install
Post by: pentium on September 17, 2008, 01:32:12 AM
Post by: pentium on September 17, 2008, 01:32:12 AM
Okay, so now that that app issue has been taken care of
how about connecting to my windows server?
how about connecting to my windows server?
Title: same as for any Unix...
Post by: cubist on September 17, 2008, 08:04:41 PM
Post by: cubist on September 17, 2008, 08:04:41 PM
SMB or NFS. Netware if you really want to go out on the edge...
Title: Cube fails to boot, even on a clean install
Post by: pentium on September 17, 2008, 08:09:19 PM
Post by: pentium on September 17, 2008, 08:09:19 PM
Oh joy.
I have never worked with either.
I have never worked with either.
Title: Cube fails to boot, even on a clean install
Post by: cubist on September 17, 2008, 08:16:33 PM
Post by: cubist on September 17, 2008, 08:16:33 PM
Quote from: "pentium"Oh joy.Joy will have little to do with it. :-) Also depends upon what you want to do. If printing, which side will serve the printer? If windows, you'll probably want the lpd-bearing tools on Windows. If NeXT, then either. Could do some other things as well...
I have never worked with either.
Title: Cube fails to boot, even on a clean install
Post by: pentium on September 17, 2008, 08:31:04 PM
Post by: pentium on September 17, 2008, 08:31:04 PM
I just want file sharing. I got a NeXT laser printer for printing. :)
Well I do have some flashy program for NFS on my server however I have never figured out how it worked. I might also be switching over from my existing Windows 2000 server to a sun Enterprise 3000 server soon so I guess NFS will have to do.
Well I do have some flashy program for NFS on my server however I have never figured out how it worked. I might also be switching over from my existing Windows 2000 server to a sun Enterprise 3000 server soon so I guess NFS will have to do.