Clean Install WB Help

[Acill]

Okay here is one I have never seen dnd I cant figure out a solution.

My A4000T has a mess on the main boot partition from years of junk and installs on it. At this point I just want to start over clean. I have a 1GB partition on the drive I decided to put a clean install of Workbench on so I can move things over from my main partition.

I boot from my emergency disk and installed 3.9 to in with no problems. When I reboot and go to the early startup to select the new drive it starts to boot and I get a requester that no disk present in device DF0?? I try again and format that partition and do another clean install with the same result.

So I boot from the A4000T 3.1 floppy and do an install of a clean 3.1 and it does the same damn thing?! Anyone have a clue why the heck it would ask for a disk to be in the floppy after a new install? I am about to see if just pulling the HD and putting a new one in with no partition other than a clean one helps, but its strange.

[QuikSanz]

I think I've been here, boot with floppy and look in Df0, see if (I think it's called) workbench.lib got copied over.

[Acill]

I do see workbench. library on the hard drive new partition. Its so strange it is looking for a didk in the floppy,  im at a loss.

[kolla]

Boot without startup sequence, then...

set echo on
execute s:startup-sequence

and see what line causes it. I am thinking maybe it is addbuffers, but normally that one runs to NIL: - do you even have a df0: drive on your system?

[Tenacious]

Shooting from the hip, my first thought was to wonder if your new 1 GB partition was set to be "Bootable".  I'm don't recall any safeguards to prevent the OS from being installed on a non-bootable one.  

To find out, go into HDToolBox, select Partition Drive.  In the next window, select the segments of the top bar that represents each partition.  Bootable (center-bottom of the window) should be checked for those partitions you would want to install an OS onto.  

If this is not the problem, simply select Cancel, and then Exit to quit the program without making changes.

[SACC-guy]

The 4000T is a bit strange because of the true scsi and ide headers.
Also, the workbench.lib was removed from rom

So, if your are using a true scsi drive, and your are using the real 4000T install set...
It's just a matter of setting the partition you want as bootable (as already shared)

Same is true of the ide drive but usually you have to cold boot, the drive light will seem to hang, wait a second and then just soft reset and it should find the ide partition.

M

[Acill]

True 4000T, true scsi,  no drives on IDE,  I used the real 4000T workbench disks. yes its flagged bootable. Using a toastscan for video so no video card to cause issues yet. Its just crazyness. Yes I have a floppy installed as well.

Also running csppc Cpu and its fine when I boot from a floppy. I am at a loss.

[SACC-guy]

Oh you have a 060/ppc card?

well, the issue may be the new partition may not have the 060/040 libs!

boot from floppy, install the small 040 and real 060 libs!

BTW, when you do a install from the floppies, it installs the 040 lib from the disk. over writing the small 040 lib

I made an install 3.1 floppy with the 060 libs...

[Acill]

Boot without startup sequence, then...

set echo on
execute s:startup-sequence

and see what line causes it. I am thinking maybe it is addbuffers, but normally that one runs to NIL: - do you even have a df0: drive on your system?

Im starting to think its got something to do with the hard drive formatting now. I disabled every partition  in early startup except the new one,  selected boot without start up sequence and still get the "no disk present in device DFO"

Im thinking of trying a new drive on the csppc scsi port. Its faster anyway. Any other ideas?

Oh if I pull the drive and put a new one in,  will my emergency disk still boot 3.9 from cd to install clean?

[SACC-guy]

Yes, it will work with a new drive.

but, deep breath, 98 percent of the issues are libs related

please try the correct small 040 libs and correct 060 lib install.

[Acill]

I'll pull the 040 and 060 libs off the cyberstorm CD and see what it does. I'm sick of dealing with it right now. Its been a lot of hours now.

[Thomas]

I wonder why it is so that people seeking for help always ignore the only useful suggestion.

This is what you should do and tell us at which command it stops with the "no disk" message:

Boot without startup sequence, then...

set echo on
execute s:startup-sequence

and see what line causes it. I am thinking maybe it is addbuffers, but normally that one runs to NIL: - do you even have a df0: drive on your system?

All other tips are valid but not related to the problem. The above is the only approach which can give a helpful information about the cause.

[Acill]

I wonder why it is so that people seeking for help always ignore the only useful suggestion.

This is what you should do and tell us at which command it stops with the "no disk" message:



All other tips are valid but not related to the problem. The above is the only approach which can give a helpful information about the cause.

If you look at a couple posts back you will see that I tried to boot with no startup and it still did that. I ended up tearing it down and put a new drive in. Its connected directly to the CSPPC now and boots great. I forgot how much work it was going from a clean system.

I have my Mediator installed, PCI Info sees all the cards on it when typed. I think i will take a break for now. I need to figure out how to get software over to install now. It may take me burning stuff to a CD-R and moving it that way.

[paul1981]

I wonder if you were installing over the top of your 'cluttered' boot partition by mistake instead of the new one. Anyway, moving on... Glad you're over the first hurdle, but personally I'd liked to have known what the problem was so that other future users can be informed if the same issue arises.

It sounded like a startup-sequence, boot priority or filesystem issue to me.

[Acill]

I wonder if you were installing over the top of your 'cluttered' boot partition by mistake instead of the new one. Anyway, moving on... Glad you're over the first hurdle, but personally I'd liked to have known what the problem was so that other future users can be informed if the same issue arises.

It sounded like a startup-sequence, boot priority or filesystem issue to me.

I am 100% sure I was not installing over my cluttered partition. I disabled it before doing an install every time. All I know that as soon as I pulled the old SCSI II drive out and put in a Ultra Wide on the CSPPC it installed and booted perfectly.

This mediator is a PITA!! I forgot how much work it takes to get it all up and working from doing it in the past on my A3000T. I'd had hoped it would of gotten easier by now, lol.