Espontaneous reboot trying to install solaris 8 on Pentium IV

I been having problems trying to install Solaris 8 for x86 platforms (2002 February edition) on an Intel Pentium IV system. This is the system spec:
Pentium IV 1.7 GHz
Intel Board D850 MV
512 RAM BUS (RIMM)
Maxtor 40 Gb two primary partitions
CD-ROM: Asus 52x
Already installed OSes: Windows 2000 Advanced Server. First Partition.
Problem: After I boot the PC with the boot diskette, and the boot process asks me for the Solaris CD 1 it asks for to methods. Jumpstar and Step Confirmation (not sure about the exact choises). Neither of both choises worked. When trying to read the Solaris CD 1 disk, it just reboots.
What should I do?
Thanks in advance for the help.

Before running the b kadb -v command I found some warning and here they are:
Warning: ACPI Tables not in reclaim memory
Then another warning appear abou ACPI:
Determing bus types and gathering hardware configuration data
Warning: Resource Conflict - both devices are added
NON-ACPI device: PNP0C01 Memory 97C0-97FFF .......
ACPI device: PNP0C01
Then... :-( another warning:
Warning: Resource conflict - both devices are added
NON ACPI device: ISY0050 Port 3F0-3F5, 3F7: IRQ 6; DMA: 2
ACPI device: Port 3F0-3F1, 3F2, 3F3, 3F4-3F5, 3F7; IRQ6; DMA: 2
After that.. everything went well, I activated the kadb and this is what I got from it:
/plattform/i86pc/kernel/unix loaded - 0x8b00 bytes read�
Sun OS Release 5.8 Version Generic 32-bit
Copyright ......
panic[CPU0]/thread= FEC17440: BAD TRAP: type=d (generic protection fault)
rp=FEC12994 addr=0
Generic protection fault
pid=0, pc= 0xFE80F346, sp=0xfe808ee4, eflags=0x10093
eip(fe(80F346), eflags(10093), ebo(fec12a08), uesp(fe808ee4)
esp(fec129c4), cr0(80050011), cr2(0), cr3(17e00), cs(158), ds(160), ss(410), es(160), fs(198), gs(1b0)
fec128c8 unix: die+9c (d, fec12994, 0, 0, 3)
fec12980 unix: trap+290()
fec12994 unix: _cmntrap+97 (e0c20160, e0d60160, 3)
fec12a08 unix: wrmsr+d()
fec12add unix: startup+98f()
fec12aec unix: genunix: main+a()
panic: entering debugger ( no dum device, continue to reboot) stopped at int 20+0xb ret
kadb[0]:
Well, what should be the problem?
thanks a lot.
/sergio

Similar Messages

Trying to install solaris 10 on sun file v210

Rebooting with command: boot net - install nowin
Boot device: /pci@1f,700000/network@2 File and args: - install nowin
1000 Mbps FDX Link up
Timeout waiting for ARP/RARP packet
Timeout waiting for ARP/RARP packet
Timeout waiting for ARP/RARP packet
Timeout waiting for ARP/RARP packet
Timeout waiting for ARP/RARP packet
4000 1000 Mbps FDX Link up
Requesting Internet address for 0:3:ba:60:36:d
I am trying to install solaris 10 (sparc) on a sun fire v210 and I get kernel dump and
the following crash messages:
Any suggestion would be very welcome indeed as this the first of 250 systems...
Lydia
SunOS Release 5.10 Version Generic_118833-33 64-bit
Copyright 1983-2006 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
WARNING: Cannot find /system/contract
/kernel/fs/sparcv9/procfs: undefined symbol 'default_copyops'
/kernel/fs/sparcv9/procfs: undefined symbol 'cpu_decay'
WARNING: mod_load: cannot load module 'procfs'
WARNING: Cannot mount /proc
WARNING: file system 'mntfs' version mismatch
WARNING: Cannot mount /etc/mnttab
WARNING: Cannot find /etc/svc/volatile
WARNING: Cannot find /system/object
/kernel/fs/sparcv9/procfs: undefined symbol 'default_copyops'
/kernel/fs/sparcv9/procfs: undefined symbol 'cpu_decay'
WARNING: mod_load: cannot load module 'procfs'
WARNING: Failed to process interrupt for ali1535d+-power0 due to down-rev nexus driver isa0
WARNING: power_attach: failed to add high-level interrupt handler.
WARNING: power button driver failed to install
WARNING: Failed to process interrupt for rmc_comm0 due to down-rev nexus driver isa0
WARNING: rmc_comm failed to install
WARNING: Could not install rmclomv driver
WARNING: Failed to process interrupt for pcf85840 due to down-rev nexus driver isa0
WARNING: i2c_0 failed to retrieve iblock cookie. Operating in POLL MODE only
fs/sockfs:sock_getfasync() not defined properly
/kernel/sys/sparcv9/c2audit: undefined symbol 'sogetpeername'
/kernel/sys/sparcv9/c2audit: undefined symbol 'sogetsockname'
WARNING: mod_load: cannot load module 'c2audit'
WARNING: c2audit: unable to resolve dependency, module 'fs/sockfs' not found
misc/consconfig:consconfig_get_usb_kb_path() not defined properly
panic[cpu1]/thread=180e000: mod_hold_stub: Couldn't load stub module misc/consconfig
000000000180b890 genunix:mod_hold_stub+1f0 (0, 185f800, 18ac878, 60000c44fb0, 1817328, 0)
%l0-3: 0000000001843ac8 000006000136e000 0000000001811cf8 0000000000000000
%l4-7: 0000000000000000 0000000000000064 0000000000000064 0000000000000001
000000000180b940 unix:stubs_common_code+30 (21dead78c0, 960010, 53555554, 0, 31f400, 0)
%l0-3: 000000000180b209 000000000180b2e1 000000123e000000 0000000000000001
%l4-7: 0000000000000000 0000000001817338 0000000000000000 0000060000c1abc0
000000000180ba10 genunix:main+134 (18accd0, 18a8800, 18364c0, 1861400, 183b400, 1814000)
%l0-3: 0000000070002000 0000000000000001 0000000000000000 0000000000000002
%l4-7: 00000000018afef8 00000000018afc00 00000000018acce0 00000000018acc00

I am using jet to do the jumpstart and the config file for jet is list below.
The install server is solaris 10 sparc
SunOS nereid 5.10 Generic_125100-10 sun4u sparc SUNW,Sun-Blade-1500
The version I am trying to install is 118855-33 (sol10-u3 - i believe). I have downloaded
the latest recommended patchset which should bring me to 118855-36 plus the latest
minor kernel patches.
nereid-root (482)>cat m1001
# Client template file
# Client: m1001 (derived from quintor.js)
# Created: Wed Mar 8 14:38:51 GMT 2006
# This file was automatically generated using 'make_template'
# Product: base_config
# Synopsys: Basic host information
# Architecture type:
# sun4c : e.g. SS1, SS2, SS IPX
# sun4d : e.g. SS1000, SS2000
# sun4e : ?
# sun4m : e.g. SS LX, SS4, SS5, SS10, SS20
# sun4u : UltraSparc - U1, U2, E3x00, E4x00 etc
# sun4u1 : E10K
# i86pc : Intel X86
# Ethernet can be obtained from the 'banner' command at OBP
# OS is one of the values you used to register the solaris media using
# the add_solaris_location command
base_config_ClientArch="sun4u"
base_config_ClientEther=00:03:ba:60:36:0d
base_config_ClientOS="sol10_u3"
# Client allocation
# The mechanism used to build this client; by default, the options listed
# in /opt/jet/etc/jumpstart.conf will be tried; you should only set this
# if this particular client needs to do something different.
base_config_client_allocation="newboot"
# products is the set of products to install after base_config; this
# should be updated automatically by make_template, so you
# will only need to change it, if you wish to omit certain
# modules when testing/debugging.
base_config_products=" custom"
# JumpStart sysidcfg information
# The sysidcfg file provides information at initial boot time so that the
# system can properly identify itself. The interface and ip address defined
# here MUST be on the same subnet as the JumpStart server. The root password
# is set here also and must be written in encrypted format. The default value
# shown here is "newroot". The timeserver is normally the IP address of the
# JumpStart server.
# nameservice examples:
# NONE
# NIS { domain_name=uk.sun.com name_server=nis.uk.sun.com(129.159.91.1) }
# or for DNS
# DNS { domain_name=uk.sun.com name_server=192.168.1.1 search=uk.sun.com }
# network_interface:
# le0, hme0
# or PRIMARY (the default interface - net in OBP)
# N.B. PRIMARY is only valid from Solaris 7 upwards
# locale:
# en_UK for Solaris 2.6
# en_GB for Solaris 7 and above
# timeserver: Where the client gets the current time from.
# Leave blank to default the the JumpStart server
# Alternatively, set to 'localhost' to trust the current
# hardware clock on the client
# terminal: terminal type (vt100/vt220/sun etc)
# security_policy: Kerberos policy (Solaris 8 +)
# protocol_ipv6: Use ipv6 or not (Solaris 8 +)
# default_route: Solaris 9 allows a default route to be set
# (ignored on all other versions of Solaris, less than 9)
base_config_sysidcfg_nameservice=NONE
base_config_sysidcfg_network_interface=PRIMARY
base_config_sysidcfg_ip_address=172.17.3.1
base_config_sysidcfg_netmask=255.255.0.0
base_config_sysidcfg_root_password="xxxxxxxxxxxx"
base_config_sysidcfg_system_locale="en_GB.ISO8859-15"
base_config_sysidcfg_timeserver=
base_config_sysidcfg_timezone="GB"
base_config_sysidcfg_terminal=vt100
base_config_sysidcfg_security_policy=NONE
base_config_sysidcfg_protocol_ipv6=no
base_config_sysidcfg_default_route=
# X86, X64 specific settings. If this is an x86 client, then you may need
# to configure these settings. They are ignored for SPARC builds.
# base_config_x86_nowin:
# This stops Solaris from trying to run windows during the install.
# the default value is yes.
# base_config_x86_console:
# Set the console to the correct tty port. This is used for doing installs
# via the serial port or the SP. b1600,v20z and v40z use ttya. lx50, v60x,
# and v65x use ttyb. NOTE: you only need to set this if you are NOT going
# to connect a keyboard and monitor to the client.
# base_config_disable_acpi:
# Disable ACPI - sometimes disabling ACPI makes the install go
# better due to how the interrupts are handled. Non-Null disables ACPI.
# base_config_x86_safetoreboot:
# The Solaris installer can't control the BIOS, therefore does not
# know if its safe to reboot the client as it may simply jumpstart
# again. If your PXE boot is a one time option, and the next reboot
# will attempt to boot from disk, then you probably want to set this
# option to "yes". Otherwise, leave it as it is so that it won't reboot
# and therefore allow you to manually change your BIOS to boot from disk.
base_config_x86_nowin=""
base_config_x86_console=""
base_config_x86_disable_acpi=""
base_config_x86_safetoreboot=""
# Want to create your own custom profile ? if so, use this variable to
# reference a file relative to the Clients/<clientname> directory, otherwise
# fill in the other details below to get toolkit to create one for you.
base_config_profile=""
# JumpStart profile information
# A limited profile can be automatically generated here. If further
# customisation is required, then you can manually create a profile in the
# client directory and reference it in the base_config_profile variable.
# Cluster:
# SUNWCrnet : Minimal. Solaris 10 only
# SUNWCreq : Required - really basic, good for testing
# SUNWCuser : User collection
# SUNWCprog : User + Developers collection
# SUNWCall : All packages
# SUNWCXall : All + OEM packages (mandatory for E10K)
# usedisk: defines the disk that the OS will be loaded on to - bootdisk
# (if this is set to rootdisk. , then the current boot disk will
# be used)
# dontuse: defines disks that should not be used..
# ** N.B. This will only be used if 'usedisk' is NOT set
# Space seperated list of disks of the form c?t?d?
# partition sizes:
# if partitions are not required simply leave blank. In order to maintain
# consistency the partitions will always use the same slice number:
# / s0
# swap s1
# /var s5
# /usr s6
# /opt s7
# at most one partition can have the size 'free' which denotes all the
# unallocated/spare space on a disk.
base_config_profile_cluster=SUNWCall
base_config_profile_usedisk=rootdisk.
base_config_profile_dontuse=""
base_config_profile_root=8192
base_config_profile_swap=4096
# If you are using VxVM and want your boot disk to look like the mirror, then
# leave slices 3 and 4 empty. If you do not care about keeping the two disks
# looking cosmetically the same, please just make sure you have two free slices
# somewhere on the disk for VxVM!
# If you are not using VxVM, then you can use s3 and s4 for whatever you wish!
base_config_profile_s3_mtpt=""
base_config_profile_s3_size=""
base_config_profile_s4_mtpt=""
base_config_profile_s4_size=""
base_config_profile_s5_mtpt=""
base_config_profile_s5_size=""
base_config_profile_s6_mtpt=""
base_config_profile_s6_size=""
# If you are using DiskSuite, the default behaviour is to use slice 7 as a
# location for metastate databases. If you are using DiskSuites default config,
# please avoid using s7 for data!
base_config_profile_s7_mtpt="/export/disk/1"
base_config_profile_s7_size="free"
# You can specify additional disks to use/configure here
# additional_disks is a space separated list of c?t?d? type disk names
# For each disk listed in additional_disks, a pair of variables of the form
# base_config_profile_disk_c?t?d?s?_mtpt="...."
# base_config_profile_disk_c?t?d?s?_size="...."
# should be defined for each slice required on the disk.
# N.B. DO NOT SET THE BOOT DISK UP HERE !
base_config_profile_additional_disks=""
base_config_profile_disk_c0t3d0s0_mtpt=""
base_config_profile_disk_c0t0d0s0_size=
# Additional locales/geos e.g. N_Europe, C_Europe
base_config_profile_add_locales=""
base_config_profile_del_locales=""
base_config_profile_add_geos=""
base_config_profile_del_geos=""
# UFS Logging
# Solaris 7 and above support UFS+, which allows for a logging filesystem
# under UFS. If you want to use this feature on any of the UFS mount points,
# please specify the mount points here, as a space seperated list, or enter
# the keyword "all" to enable logging on all UFS filesystems.
# Solaris 9 09/04 enables logging by default. You can also specify mountpoints
# preceded by a - sign to say that you DON'T want logging enabled on that
# filesystem, or you can use the keyword "none" to say you don't want any
# ufs logging turned on at all.
# N.B. root (/) can be included in the list, and is included by default if
# using either the "all" or "none" keyword.
# Finally, you can't mix keywords and mountpoints. i.e. "all -/" is NOT
# valid.
# e.g. base_config_ufs_logging_filesys="all" : log all filesystems
# base_config_ufs_logging_filesys="none" : log no filesystems
# base_config_ufs_logging_filesys="-/ /var -/usr" : log /var, but not / and /usr.
base_config_ufs_logging_filesys="all"
# Packages to add to/remove from the selected cluster
# Use this to populate the profile with package <pkg> <add|delete> entries
base_config_profile_add_packages=""
base_config_profile_del_packages="SFWrpm SFWexpct SUNWzebrar SUNWa2psr SUNWmysqlr SUNWffiltersr SUNWopensslr SUNWserr SUNWsmbar SUNWa2psu SUNWant SUNWbison SUNWflexlex SUNWfreetype2 SUNWggrp SUNWgimpprint SUNWgm4 SUNWgnome-a11y-gok SUNWgnome-a11y-reader SUNWgnome-camera SUNWgnome-games SUNWgnome-img-editor SUNWgnome-img-viewer SUNWgnome-media-player SUNWgnome-project SUNWgscr SUNWgtar SUNWGtku SUNWhpijs SUNWimagick SUNWmozilla SUNWmoznspr-devel SUNWmysqlt SUNWmysqlu SUNWncft SUNWopenjade SUNWopensp SUNWopenssl-commands SUNWpsutils SUNWPython SUNWsmbac SUNWsmbau SUNWsmcmd SUNWTcl SUNWtexi SUNWTk SUNWwebminu SUNWwgetu SUNWzsh SUNWjavaapps SUNWmozapoc-adapter SUNWmozchat SUNWmozdom-inspector SUNWmozgm SUNWmozilla-devel SUNWmozjs-debugger SUNWmozmail SUNWmoznspr SUNWmoznss SUNWmoznss-devel SUNWmozpsm SUNWmozspell SUNWopenjade-devel SUNWopenjade-root SUNWopenjade-share SUNWopensp-devel SUNWopensp-root SUNWopensp-share SUNWseru SUNWserweb SUNWsfinf SUNWsfman SUNWsmdoc SUNWzebrau SUNWpostgr SUNWpostgr-contrib SUNWpostgr-docs SUNWpostgr-jdbc SUNWpostgr-libs SUNWpostgr-pl SUNWpostgr-server SUNWpostgr-server-data SUNWpostgr-tcl"
# Clusters to add to/remove
# Use this to populate the profile with cluster <cluster> <add|delete> entries
base_config_profile_add_clusters=""
base_config_profile_del_clusters="SUNWCpm SUNWCpmx SUNWCdial SUNWCdialx"
# Remote file systems (NFS)
# Specify these as space seperated list of pairs as follows, using ? as
# the seperator (as : has special meanings with nfs!)
# e.g. to mount 1.1.1.1:/fs on /fs you would create the entry
# base_config_nfs_mounts="fs?1.1.1.1:/fs"
base_config_nfs_mounts=""
# Host information
# This section defines most things network related etc.
# In addtion, if the machine will be JumpStarted as one name/address and
# needs to have a different name/address once installed, this is where you
# can set that information.
# nodename: the value for /etc/nodename if it's not the default
# hostname
# defaultrouter: the value for /etc/defaultrouter.
# notrouter: if this is set, the file /etc/notrouter will be created
# dns_domain: domain entry for /etc/resolv.conf
# dns_nameservers: nameserver entries for /etc/resolv.conf
# (list of ip addresses, space separated)
# dns_searchpath: list of entries to go in the search line
# dns_disableforbuild: If there is no DNS available in the build
# environment, set this to delay the configuration
# of DNS until later on.
base_config_nodename=""
base_config_defaultrouter=""
base_config_notrouter=""
base_config_dns_domain=""
base_config_dns_nameservers=""
base_config_dns_searchpath=""
base_config_dns_disableforbuild="yes"
# NTP configuration
# Specify a list of names or ip addresses for the NTP servers. The first
# one will be given a 'prefer' tag. This section will only place lines
# of the form: server <ipaddress/name> [prefer]
# into the /etc/inet/ntp.conf file. If you require more control of ntp,
# please use the custom module to deploy your own custom ntp.conf file.
# N.B. If you do use names, they must be resolvable in your name service.
base_config_ntp_servers=""
# Network Interface information
# networkifs: a list of interfaces to be defined,
# space seperated "le0 hme0".
# N.B. the sysidcfg interface will already be configured
# Logical interfaces should be defined using _'s rather
# than :'s.
# networkif_<ifname>: the details of the interface <if>
# "netname netmask hostname address"
# netname: arbritrary name for /etc/networks
# netmask: netmask of this if (e.g. 255.255.255.0)
# hostname: unique hostname (N.B. not multihomed)
# address: IP address of this interface
# For example:
# base_config_networkifs="ge0 ge0_1"
# base_config_networkif_ge0="bkp 255.255.255.0 me-bkp 192.168.1.0"
# base_config_networkif_ge0_1="bkp2 255.255.255.0 me-bkp2 192.168.2.0"
base_config_networkifs="beg1"
base_config_networkif_beg1="data 255.255.0.0 d1001 172.18.3.1"
# N.B. Logical interfaces MUST use _ rather than : as illustrated below
base_config_networkif_le0_1=""
# IP Multipathing (Solaris 8+)
# IPMP default mode is automatic failback.
# To change this mode edit /etc/default/mpathd
# ipmp_networkifs: a list of interfaces to be defined under ipmp control
# a space separated list of pairs only
# e.g. "qfe0_qfe4 qfe1_qfe5"
# N.B. If the primary interface is used in an ipmp group, the
# system must be rebooted manually after installation to
# activate ipmp.
# N.B. Can only setup ipmp group with pairs of interfaces in one
# of the following configurations:
# active-standby failover:
# Set ipmp mode = s, and specify one logical
# hostname/ip address pair.
# failover with outbound load spreading:
# Set ipmp mode = l, and specify one logical
# hostname/ip address pair.
# active-active with outbound load spreading:
# Set ipmp mode = l, specify a second logical
# hostname/ip address pair for the second interface.
# ipmp_networkif_<if>_<if>: "netgroup mode test1 test2 mask hostname log-ip hostname2 log-ip2"
# details of the interfaces in the ipmp group
# e.g. networkif_ipmp_qfe0_qfe4
# netgroup: ipmp interface group name
# e.g. database-net
# ipmp mode: s = standby (failover only)
# ** test addresses are allocated last,
# ** first test address will be on the
# ** first virtual interface of the
# ** first physical adapter. Second
# ** test address will be on the second
# ** physical adapter.
# l = load spreading / active-active
# ** test addresses are allocated on
# ** first virtual interfaces on both
# ** the first and second physical
# ** adapters.
# To force the test addresses onto the physical
# adapters, use the suffix 'p' to the above
# modes, i.e. 'sp' or 'lp'. This is not
# recommended and may break certain applications.
# test1: ipmp test address1
# test2: ipmp test address2
# N.B. these addresses must not be used or
# placed in the hosts file
# mask: netmask for ipmp pair
# hostname: unique hostname for logical ip
# log-ip: logical ip address for first i/f of pair
# N.B. The following two parameters are for active-active
# configurations only. Do not specify them for an
# active-standby configuration.
# hostname2: unique hostname for logical ip
# log-ip2: logical ip address for second i/f
# of pair
# Example:
# base_config_ipmp_networkifs="qfe0_qfe1"
# base_config_ipmp_networkif_qfe0_qfe1="database-net l 10.0.0.1 10.0.0.2 24 oracle-db 10.0.0.3 apache 10.0.0.4"
base_config_ipmp_networkifs=""
base_config_ipmp_networkif_qfe0_qfe1=""
# Misc options
# this section is a catchall for other options not included above
# update_terminal: if set, put the sysidcfg terminal type into inittab
# enable_savecore: if set to any value, enable save core (Solaris 2.6 only)
# dumpadm_minfree: set a limit so that crash dumps don't fill up the
# dump filesystem. See dumpadm(1M) -m option for
# possible values.
# noautoshutdown: if set to any value, disable power management
# enable_rootlogin: if set to any value, enable network root login
# from both telnet/rsh and ssh
# enable_rootftp: if set to any value, enable root ftp access
# shutup_sendmail: if set, create an alias hostname. to shut up sendmail
# poweroff_afterbuild: if set, shut the machine down once it has been built
# base_config_dedicated_dump_device:
# if set, dumpadm will configure the partition as a
# Dedicated Dump Device. See dumpadm(1M) for supported
# Operating Environments.
# (Device path e.g. /dev/dsk/c?t?d?s?)
# N.B. This partition is for the SOLE use of the crashdump utility !
# enable_altbreak: if set, enable alternate break sequence
# disable_sysid_probe: if set, skip the sysid stuff on the first reboot; this
# usually just tries to rarp ip addresses for additional
# interfaces and takes ages on machines with lots
# of unused network adapters.
base_config_update_terminal="yes"
base_config_enable_savecore="yes"
base_config_dumpadm_minfree="20000k"
base_config_noautoshutdown="pm_disabled"
base_config_enable_rootlogin="yes"
base_config_enable_rootftp=""
base_config_shutup_sendmail=""
base_config_poweroff_afterbuild=""
base_config_dedicated_dump_device=""
base_config_enable_altbreak=""
base_config_disable_sysid_probe="yes"
# NFSv4
# Set up the NFSv4 domain to prevent being prompted at first reboot.
# If not set, this will default to the entry in base_config_dns_domain,
# and if that is not set, to the value 'domain', which is the default
# in /etc/default/nfs
base_config_nfsv4_domain=""
# N.B. Unless you need to point this client at alternate media for patches
# and packages that is not held on this server, please skip this section!
# productdir is where to find the products. This should be an NFS style
# path, i.e. 192.168.1.1:/export/install but if the server
# is the JumpStart server, then it should just be specified
# as a normal path.
# patchdir is where to find the patches. Same format as productdir.
# Leaving the following blank means they will be populated using jumpstart.conf
# and the JumpStart servers ip address. This is the default behaviour
# and should only be changed if your patch/package repository is not held
# on this server.
base_config_productdir=""
base_config_patchdir=""
# Last one - mainly for developing JumpStart scripts!
# If you set this, the rc3.d/S99jumpstart script will be disabled
# (set to rc3.d/s99jumpstart) every time it is processed - this allows you
# to run it by hand and invoke each reboot step
base_config_debug_jumpstart_postinstall=""
# Product: Custom
# Synopsis: The custom product can install packages and patches that
# would not otherwise be included by the standard
# installation products.
# Which additional packages are to be installed
# (by default, these get added during the main Solaris installation phase)
# O.S. Specific versions:
# as a side effect, if a directory exists under the package dir named
# after the OS, (uname -r), the subdirectory will be used instead of the
# main package directory
# i.e /export/install/pkgs/custom/sparc/5.8 takes preference over
# /export/install/pkgs/custom/sparc for a Solaris 8 box
# Package Response files:
# If a custom package needs a response file, create a directory called
# /opt/jet/Clients/<clientname>/responses
# and put the response file in to it, named the same as the package.
# i.e. for a package called Fred, on client1, use pkgask to create
# pkgask -r /opt/jet/Clients/client1/responses/Fred Fred
# (Space seperated list of packages)
custom_packages=""
# Custom packages at subsequent boots
custom_packages_1=""
custom_packages_n=""
# Which additional patches are to be installed
# (by default, these get added during the main Solaris installation phase)
# (Space seperated list of patches)
custom_patches=""
# Custom patches at subsequent boots
custom_patches_1=""
custom_patches_n=""
# Custom patch sets... create a directory in the patch directory named after
# the set, and put a patch_order file in it, along with the patches...
# (Space seperated list of patch set names)
# N.B. as a side effect, if a directory exists under the patch set dir named
# after the OS, (uname -r), the subdirectory will be used instead of the
# main patchset directory
# i.e /export/install/patches/patchset/5.8 takes preference over
# /export/install/patches/patchset
custom_patchsets=""
# Custom patchsets at subsequent boots
custom_patchsets_1=""
custom_patchsets_n=""
# Search paths
# The files and scripts sections below will look for source files relative
# to the Clients/<clientname> directory. If you wish to look in other places
# for files, please fill out the search path option below. Items in the
# search path are relative to the Clients/<clientname> directory, since the
# client has no knowledge of the filesystem layout of the server
# e.g. for a client 'fred', the default location for all custom files/scripts
# is /opt/jet/Clients/fred
# if the search path was set to "../common" then the installation routines
# would look first in Clients/fred then
# Clients/fred/../common (or Clients/common in this case)
# Search path is a space separated list of places to search
# THE SEARCHPATH IS ONLY VALID FOR files & scripts. NOT PACKAGES/PATCHES!
custom_search_path="../common.files"
# Files to be copied to the client. The filenames must be of the form
# filename1:a:filename2
# Where filename1 is the name of the source file in the
# /opt/jet/Clients/<clientname> directory
# filename2 is the full path of the file on the installed client
# and the middle option is whether to a - append, or o - overwrite the file
# (by default, these get added during the main Solaris installation phase)
# (Space seperated list of tuples)
# N.B. Please see section above regarding where to place the source files
# N.B. (2):
# appending to /etc/hosts is a special case; instead of just appending
# the file, the module will do an 'intelligent merge' of the new hosts
# file with the existing one.
# custom_files="hosts:a:/etc/hosts"
#custom_files="system:a:/etc/system"
custom_files=""
custom_files_1="NISHost:a:/etc/inet/hosts QuintorNFS:a:/etc/vfstab authorized_keys:o:/.ssh/authorized_keys SGEServices:a:/etc/services"
# Custom files at subsequent boots
custom_files_n=""
# Scripts to be run on the client at the end of the build
# The scripts must be placed in the directory
# /opt/jet/Clients/<clientname>
# and will be copied to the client.
# Note: we don't allow you to run custom scripts during the Jumpstart
# phase because its kinda dangerous.
# If you need to do this, the best way is to create
# your own custom module to do this.
# Custom scripts at subsequent boots
custom_scripts_1="DurhamUni_PostInstall.ksh fixup_ssh"
custom_scripts_n=""
# Special JumpStart 'Begin' phase scripts
# If you need to run scripts in the 'begin' phase of the JumpStart, you
# can supply them here. Please note, that in the 'begin' phase, the
# new OS has not been installed and the majority of the OS running will
# be read-only from the JumpStart server.
custom_scripts_b=""
nereid-root (483)>

Getting an error 'Cannot open Boot device' while trying to install Solaris

Hi,
We were trying to install Solaris * on a Sun Sparc system and the CD rom drive does not seem to get recognised. When we try booting from cd rom we get an error 'Cannot open boot device' .
This server was up & running and we were trying to remove a hard disk that had failed and modified the vfstab script . After that the system failed to even boot up. So when we tried reinstalling the OS we are running into this problem.
Am new to this technology ...And any help would be greatly appreciated. .....
Thanks

Cdrom drive must be scsi device 6
I assume you are running < boot cdrom> at the ok prompt
also at the ok prompt run the command <probe-scsi> (without the angled brackets) you need to see the following:
Target 6
Unit 0 Removable read only device TOSHIBA XM.......bigpileofnumbers
If not, check the cdrom drive and the cdrom inside
hope this helps
Alan

"Non-system disk Press any key to reboot"- Trying to install Win 7 on Mac Mini

Hello. I'm trying to install Windows 7 on a new-model Mac Mini ('Late 2012'), which I just bought from Apple. [Specs: 1 TB Fusion drive, 2.6 GHz intel Core i7, 16 GB RAM, OS X Mavericks (latest), Graphics: Intel HD graphics 4000, Screen: LG Flatron 24"].
After following instructions on Bootcamp, I tried installing it through my external USB Apple Superdrive (DVD), but for some reason as soon as the system finishes getting things ready and reboots to begin installing Windows 7, I get a black screen with an error message as follows: "No bootable device -- insert boot disk and press any key". Pressing the keys on my keyboard does nothing (even though it's a wired model, not a wireless one.) I'm forced to do a hard shutdown using the power button and hold down the Option key in order to get the system to show the Mac HD where OS X is. It also shows the Windows DVD as another option, but when I select it and the system boots, I just get the same error message again. So I go back to a hard shutdown and reboot to go into OS X again.
Not sure what to do, I did some online research and in one post in the Frequently Asked Questions for Bootcamp, it says for installing Win 7 and Win 8, the computer won't work with external USB drives (*totally nuts in my opinion - Apple has to fix this stuff if they want to entice Windows users into buying their sleek, quiet hardware). Instead, the post recommends creating a Windows 7 ISO file from my Windows 7 DVD and putting it on a USB thumbdrive that Bootcamp is going to use to put all the Apple/Windows drivers on for the installation process. I'm also told I have to unplug my Superdrive (no explanation given for why). So I do all this and get Bootcamp Assistant running again. Unfortunately, as soon as the system reboots after going through all the usual preparation steps, I get another black screen with a new error message: "Non-system disk Press any key to reboot". So I'm at a loss for what to do next.
(I've also have an iMac that I bought more than a year ago that I also put Windows 7 on, with no problems that time. Go figure.)
If anyone here has an good answer for how to proceed, I need to know. Thanks in advance!

Here they are:
cygnus-x1:~ LantS$ diskutil list
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *121.3 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:          Apple_CoreStorage                         121.0 GB   disk0s2
   3:                 Apple_Boot Boot OS X               134.2 MB   disk0s3
/dev/disk1
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk1
   1:                        EFI EFI                     209.7 MB   disk1s1
   2:          Apple_CoreStorage                         443.3 GB   disk1s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk1s3
   4:       Microsoft Basic Data BOOTCAMP                556.0 GB   disk1s4
/dev/disk2
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                  Apple_HFS Freedom (Mac HD 1 TB) *555.8 GB   disk2
/dev/disk3
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     FDisk_partition_scheme                        *16.0 GB    disk3
   1:                 DOS_FAT_32 WININSTALL              16.0 GB    disk3s1
cygnus-x1:~ LantS$ diskutil cs list
CoreStorage logical volume groups (1 found)
|
+-- Logical Volume Group DB9C188B-5B09-43DE-BA9A-1CBB53ED19C4
    =========================================================
    Name:         Macintosh HD
    Status:       Online
    Size:         564333961216 B (564.3 GB)
    Free Space:   49152 B (49.2 KB)
    |
    +-< Physical Volume 415AE4A2-2CDB-4C8B-AE00-7A14014B3EA0
    |   ----------------------------------------------------
    |   Index:    0
    |   Disk:     disk0s2
    |   Status:   Online
    |   Size:     120988852224 B (121.0 GB)
    |
    +-< Physical Volume 829492A1-0BC2-4358-A778-C008C03D00F7
    |   ----------------------------------------------------
    |   Index:    1
    |   Disk:     disk1s2
    |   Status:   Online
    |   Size:     443345108992 B (443.3 GB)
    |
    +-> Logical Volume Family C37DA9C0-00E7-46A4-90EC-548204BFB908
        Encryption Status:       Unlocked
        Encryption Type:         None
        Conversion Status:       NoConversion
        Conversion Direction:    -none-
        Has Encrypted Extents:   No
        Fully Secure:            No
        Passphrase Required:     No
        |
        +-> Logical Volume B769E601-F56F-4F83-A5B5-4378159FF8B9
            Disk:                  disk2
            Status:                Online
            Size (Total):          555826479104 B (555.8 GB)
            Conversion Progress:   -none-
            Revertible:            No
            LV Name:               Freedom (Mac HD 1 TB)
            Volume Name:           Freedom (Mac HD 1 TB)
            Content Hint:          Apple_HFS
cygnus-x1:~ LantS$

Trying to install solaris on my laptop with no success...

Tried to install either sol-10-u9-ga-sparc-dvd.iso or sol-11-exp-201011-ai-sparc.iso on my laptop that's got both windows 7 and openSuse installed. I can open the files both with magic disk and undisk. All they do is show me the files that are within the iso of each, but I can't seem to boot. Hell, I can't even copy the images to a disk as the software says it can't! I really don't want to as I have magic ISO that allows me to mount the files as a virtual disk, but as I open those drives, I get the same ol' file contents. I'm expecting the installation wizard to just magically open up, but that's not happening. Can someone shed some light on this problem?
Daniel

Ok. I reburned a DVD making a correct image file unlike the first disk I made. Apparently I thought I did it right the first time. I just tried some other way and found that is the right way. Now I was able to boot and the disk installed Solaris "supposedly". Now on the GRUB there is no choice for booting Solaris, so thought I should boot from the DVD. This made the computer try to reinstall Solaris. Does anyone know what I can do next?
And now for some reason the computer won't recognize my external HD.
Thanks,
Daniel
Edited by: 839343 on Feb 25, 2011 9:00 PM

We can't install Solaris 8 - IBM PC SERVER 315

Hello:
We are trying to install Solaris 8 (Intel) (02/02) in an IBM PC Server 315.
Some words about it:
- 128 Mb RAM
- Pentium Pro 200 Mhz
- Adaptec AHA-2940U/2940UW Ultra SCSI in PCI bus1,Slot 4 (Info from Solaris install) (Target 7)
- Hard Disk IBM SCSI (Target 0)
- CD-Rom SCSI IBM CDRM00203 (Target 6 of SCSI) (info from Solaris install)
We have a big problem.
We can't install Solaris from CD.
After Loading kernel , when it begins Searching /dev and /devices...we see this text in the screen repeated a lot of times:
WARNING: /pci@0,0/pci1011,24@2/pci9004,8178@1(adp0):
timeout: abort device, target=6 lun=0
And before this something like it has some problem and begins a resinc ??
Please Could you help us?
Solaris has been purchased from Sun on 12 March 2002
A lot of Thank's!
P.D: Please, excuse my poor English.
A lot of thank's.

two other severs wouldn't run the cd either? Break it down a little it will be more solvable. We will create two separate problems with this. First we will check the cd disk itself. Put in another system and install solaris. If that works, move to the cdrom drive....move it to the same computer you just installed solaris on...if it works then it is another problem.

Problem installing Solaris 10 onto CP1500

I'm trying to install Solaris 10 11/06 onto a CP1500 (UlraSparc-IIi, 440MHZ, 1GB RAM, OpenBoot 3.10.24, using a PS/2 Keyboard). The install CD boots up, but soon after the initial boot (after it displays copyright information but before the installer starts) it goes into a state where it syncs the file system, then reboots. If set to boot from the CD-ROM, it just goes through this process in an continuous loop: boot, cut to file system sync, reboot, cut to file system sync, reboot, wash, rinse, repeat to infinity. The acutal file system sync happens in the blink of an eye. I don't believe that this has anything to do with the state of the hard disk, as it does this even when the hard disk is disconnected from the SCSI bus.
I'm installing from an IDE CD-ROM drive that is connected to the SCSI bus using an adapter. I've sucessfully installed Solaris 8 onto this system, but alas, I need Solaris 10.
Does anyone have any idea what might be causing this? Any help would be appreciated.
Thanks!

I downloaded the latest version of Solaris 10, and that solved the problem of the continual reboots. Now the keyboard doesn't work, but that's a different problem.

Resource Conflict Warning (ACPI/NON-ACPI devices) while installing solaris

Hi,
I am trying to install Solaris 8 on my system.
Intel Celeron 1.7 Ghz
128 MB RAM
Gigabyte 8LD 533K Motherboard with Intel Chipset.
While installing, the second installation screen titled "Bus
Enumeration" gives the following warning.
Warning: Resource Conflict:
ACPI Device: PNP0C01.
Memory: (about 5 to 6 memory addresses in hexadecimal form are shown)
NON-ACPI Device: PNP0C01.
Memory: (about 5 to 6 memory addresses in hexadecimal form are shown,
which are different from the ones shown under the ACPI device list)
I ignored the message and pressed F2 key as suggested.
The next screen "Solaris Boot" comes and after choosing the CD (as
the target from which the OS is to be installed), The next screen
comes up asking me to chose the type of installation 1) Solaris
Interactive and 2) Jumpstart. No matter which option I choose, the
system shows 2-3 messages, and even before I can read them, the
system reboots. Thus I am unable to install Solaris.
I searched on Google and as one person had suggested tried tweaking
the BIOS. (Disable APM etc). But it did not work, because I don't
have an option that specifically gives the Disable/Enable option for
APM. I get the Advanced Power Management screen, but it shows some
different options.
I spoke about this problem with a friend who has some experience on
Solaris and he put the CD Drive and the Hard Disk on two different
buses, but it didn't help. I still get the same message.
I would be very grateful if someone could suggest a method so I can
install Solaris.
Regards,
pmu

The next screen comes up asking me to chose the type of installation 1) Solaris
Interactive and 2) Jumpstart. At this screen, type
b kadb -v
instead of choosing 1) or 2). Now you should be able to read the error messages from the kernel that
prevent booting into Solaris.

Partitions problems installing solaris 8 2/04 on Sun v240

Hi all,
I'm trying to install Solaris 8 on a v240 sun machine. The machine is new, and I think it comes with Solaris 10 installation files pre-loaded. I don't want them, I need Solaris 8.
I'm starting installation booting from cd to use my Solaris 8 cds. During initial installation steps the system promts following question:
Searching for a location to place the Solaris installation software...
Searching disks for upgradeable Solaris root devices...
The following root devices were found to be upgradeable:
Release Root Device
Solaris 10 c1t0d0s0
Swap slices are usually erased at each reboot, so it is preferable
to place the Solaris installation software on a disk slice labeled swap.
The disk slice, c1t0d0s1, labeled as swap,
is large enough to hold the Solaris installation software.
NOTE: All information on the selected swap slice will be erased.
Can c1t0d0s1 be used for the Solaris installation software [y,n,?,q] y
And I need to choose one to go on. Then, when I reach the step to set disk partioning up it tells me that I have to do it using cylinders. I try it, but the slice that is being used in the first step (see above) to store installation files is named as swap and I cannot edit it.
How can I proceed? I want to edit my partioning during installation process as I always have done when installed Solaris before.
What is goin on? any help?
Thanks a lot in advance!!!

Since this is a fresh installation, you might consider starting it all over again.
You may have made some initial selections while prompted at the beginning of the install process, that accidentally omitted essential system files.
As for that device path and the disk? It's pointing to an external non-Sun peripheral that's connected to the rear external SCSI port. That drive has some bad sectors. ( I wouldn't trust a new OS on those sectors until you fixed them.)
The errors are not calling out either of the two possible internal drives.
Infodoc 21216 lists a few default system device paths, and ...Sun Fire [TM]v120 / Netra[TM] 120
PCI slot 0               /pci@1f,0/pci@1/<device>@1,*          33mhz-32bit-5V
disk 1                    /pci@1f,0/pci@1,1/scsi@8/sd@0,0
disk 2                       /pci@1f,0/pci@1,1/scsi@8/sd@1,0
External SCSI Port          /pci@1f,0/pci@1/scsi@8,1/<device>
CDROM                    /pci@1f,0/pci@1,1/ide@d/sd@0,0
Network 1               /pci@1f,0/pci@1,1/<network>@c,1
Network 2               /pci@1f,0/pci@1,1/<network>@5,1

Installing Solaris 8 on Dell GX 240 (Intel P4)

While trying to installing Solaris 8 that I purchased from Sun, the installation process never gets to writing/formating the hard drive. Each time it gets to the menu to choose installation method, the system reboots after running a few more processes. It keeps doing the same thing over and over and I do not see an error message.
Please help.
Mark

Because 3Com changed the code on the 3C905C-TX interface and sun no longer recognizes it. 3Com has drivers for it on their website but I have yet to figure out to install the drivers. I have heard that it does work.

Install Solaris 8 on SPARC system

Hi,
I'm new in Unix/Solaris. I tried to install solaris 8 on a sparc system, I downloaded (SOL-8-1_01-FCS-BIN-SPARC-V1 and V2) and i burned 2 CD as. On the sparc system is already SUNOS 5.6 installed. But each time I tried to boot the system it "hang" after the message:" starting rpc services: rcpbind keyserv nis_cachemgr done." What ever I type after this message has no effect at all. I'm allowed to format the disk (home user). The CD-rom player is attached to the Sparc but can not boot the CD. Is there anyone who can help me.
I downloaden olso the pdf files but they were no use for me at this moment.

Hello,
you will have to go to OK prompt and then boot with CDROM.
1.login as root and then type
#eeprom auto-boot?=false
2.reboot the system. the system will stop at the OK prompt.
3. then type:
OK boot cdrom install
you should see Solaris install program and follow its instruction.
And the error you see seems to be caused by bad network connection

Installing Solaris 9 on an x86 platform with win98 and win2K

Hi,
There is a Pentium P4 (2.4 GHz) machine with a 40 GB hard disk...
This has 1 primary partition and the remaining is the extended dos partition. In effect there are the following logical drives - C, D, E and F. These are FAT32 partitions and have WIN98 and WIN2K (server) installed on them.
There is a free space of abt 8 GB remaining on which i am trying to install Solaris 9 (via CD). But am just not able to do so.
During the process, i get to the step saying that my disk is to be partitioned and that i could either choose the DEFAULT LAYOUT or manually partition the disk with the fdisk.
Default layout indicates that there would be 1 x86 partition (primary, boot) and the remaining would be a solaris partition - implying that all my other data would get formatted out!!!
When i try to use the fdisk to manually partition the disk, the free space mntd above does not show up!!!
But this is seen when i use the DOS fdisk - i.e. i could create a logical drive on the extended dos partition...
Can some one please help me install the Solaris in the free space i have ?? Thanks.

Hello!
There is one simple method also..
Instead of Installation disk of Solaris, insert the Software 1/2 Disk, and try to follow the actuall Suninstall method of installing Solaris. Here you will get the option that how to utilize the free space.
I myself have installed more 5 OS on a single Hard disk :) this way. Try this method

Lot of troubles (impossible) installing Solaris 10 on VMware Workstation 6

Hi, i'm experiencing troubles trying to install Solaris 10 x_86 (the last release) on VMware Workstation 6.
During the creation of the virtual machine I selected Solaris 64bit (I'm running an Intel Core2Duo CPU), selected the first ISO image and boot up the virtual machine. The installation of the first cd went just fine.
During the installation of the second cd, at a certain percent (sometimes ~50%, or later) the virtual machine reboots: I select the first choice on grub menu, but Solaris tolds me that something about the root repository (I don't remember well) is out of sync, and suggest me to reboot in failsafe mode and repair it; I did it and reboot...Doing this way I installed the second cd, but for the third (it happened the same -reboot- problem) it didn't work:
after fixed the repository in failsafe mode, and after reboot it doesn't start the installer, and shows this message:
http://img469.imageshack.us/my.php?image=solarishangsoi3.png
Please help me! I don't really know where/what I'm doing wrong...
Thanks really a lot for any help.
Regards
Gabriele

Simply Great, I had to Reboot the OS and I went to Failsafe mode where it went to single user mode and ask to update boot_archive, that worked.
When i Shutdown and Rebooted the System i could see system booting nicely and then it gave me bunch of Errors.
I think i will go and Do a Fresh Install again :(

Installing Solaris 8 under STL2

Hi!
I'm trying to install Solaris under a single PentiumIII 1Gz Stl2, with 256 RAM.
I've upgraded BIOS to version 1.1, as Intel says it's the only version with which solaris runs.
I've also tryed to set
setprop acpi-user-options '0x2'
with no luck.
The syntoms are that when the kernel starts, it dumps a page of errors, which I'v no time to read as it reboots immediately.
Any hints?
TIA!!

Because 3Com changed the code on the 3C905C-TX interface and sun no longer recognizes it. 3Com has drivers for it on their website but I have yet to figure out to install the drivers. I have heard that it does work.

Problems installing Solaris 8 w/ Win2k

Hi all,
I tried to install Solaris 8 IA today on a hard drive that previously had Win2000. I ran into many problems and am incredibly frustrated, so please forgive me. I hope somebody can help.
In essence, I installed Solaris 8, and it looks like it changed my MBR for the worse. I managed to fix part of this, but I later found out it completely re-arranged my Win32 drive letters, rendering my Win2k partition practically unusable.
Here is how my two hard disks were laid out before the install:
HDD-0 (IBM DeskStar 60G) -- Primary IDE Master
25G allocated to a bootable Win2k partition w/ NTFS, mapped as drive "F:\"
35G unallocated, unformated space
HDD-1 (WD Caviar 4G) -- Primary IDE Slave
2G bootable Win95 w/ FAT-16, mapped as drive "C:\"
1G Win95 extended w/ FAT-32, mapped as drive "D:\"
71M Linux swap w/ ext2fs
700M Linux native w/ ext2fs
Points:
I am completely uninterested with the MBR of HDD-1. This is just a hard drive I moved over from my old computer that I still use because it has all of my data on it. I no longer boot any OSes from this drive. (BIOS boots to HDD-0.)
When I installed Win2k a month or two ago, it detected my HDD-1 partitions and labelled them as "C:\" and "D:\" (their previous labels when installed on my old computer), and I was forced to make my new Win2k partition on HDD-0 "F:\". I thought this would be a good idea anyway, since I didn't feel like changing all of my old shortcuts, preferences, etc. for my apps on HDD-1.
When I installed Solaris 8 (4/01) today, I gave it about 12G on HDD-0. It seems like I got the whole partitions thing to work well, and after the install, using the Software 1 of 2 CD, it rebooted the computer (as it said it would). I took the CD out, and as it went to boot HDD-0, I got the dreaded "Bad PBR sig". I immediately knew my MBR was messed up.
Now I couldn't boot to Win2k because Solaris was my active partition. I was able to use the Win2k install CD to deactivate the Solaris partition, but I was floored to learn that my drive assignments were completely changed. My F became C, C became D, and D became E. The natural consequence of this was that I couldn't boot Win2k, because my video drivers, etc. are configured to be on "F:\...", which of course doesn't exist. My solution to this was to install another Win2k setup on the same partition (dirty, but works).
Questions:
1) How the heck do I get my original drive assignments back in Win2k? I don't want to have to change all of my setup files to point to C instead of F, D instead of C, etc. (I don't even think this is feasible.) Nor do I want to re-install all of my software. The Win2k install CD and Adminstrative Tools don't seem to provide any way to do this. Is there some (free) partition software I can download to correct this? Can the Solaris fdisk do this?
2) What's up with Solaris? How do I get this to work? I can boot the HD installation from the CD, but I can't do much because my video card apparently isn't supported and so everything comes up yucky. But how can I boot it without the CD and with a dual boot option? Is this one of those "you can't put boot code outside the first 1024 cylinders, yada, yada, yada" deals? If so, just shoot me now. <g>
Any help would be greatly appreciated. I blew the whole day on this. It pains me to say this, but... I know we all crack on Microshaft's business practices, but, FWIW, I installed Win2k in about 30 minutes, with not a single problem, with all devices being configured properly and having drivers, and haven't encountered a glitch since. I think that has a lot to do with their "popularity". There needs to be serious competition.
Thanks,
John
PS: I don't have access to e-mail until this is cleared up, so please post here.

Well, this is my solution to my problem:
I was able to install a second Win2k on my first hard drive to at least get back to my Win2k stuff. This leaves a total mess though, because now I have two user accounts, two installations, files pointing to the wrong place, registry settings all messed up, drivers installed twice, etc. So what I'm going to do is go ahead and install Linux, leave my Solaris partition alone (I think it's okay, though I can't boot to it w/o the CD), backup all the Win2k data and files I want to keep (not much -- it's a fresh computer), and then reformat my Win2k partition and reinstall Win2k.
The thing I'm still hazy on is the whole "1024 cylinders" issue. I'm not sure if I have to re-partition my hard drive, etc.
When you install Solaris, be sure to remember that Solaris and Linux swap use the same code (0x82 I think it is) for the partition. Read the Solaris documentation to make sure, but I think after you install Solaris you might have to reinstall Linux, or something like that.
Good luck. This is very confusing. I'm disappointed with the lack of documentation for installing Solaris. What did I pay $45 for? Thirty-five different translations of the same skimpy docs? Terrible. At least M$ takes care of its customers.
John

Espontaneous reboot trying to install solaris 8 on Pentium IV

Similar Messages

Maybe you are looking for