Re: Desktop Switched between two hard drives
Don,
Thanks for the reply. We've never had a need for dual-boot. We've always
booted from the C: drive, and allowed the D: drive to hold our management
software and data. All machines in the office are running Windows 98SE. They
all saw the server as the "S:\" drive and could all access the server and
software with only an occasional "burp" that I easily fixed.
Last Saturday, 8/18, the server froze up as I was using our management
software on the D: drive; even Task Manager wouldn't appear. So, I manually
powered down. When I re-booted, it booted normally to its regular desktop,
but when I attempted to access my software again, I received a "conmode.dll"
error message. I went to the web site of the compiler and downloaded their
update for the conmode.dll file; re-booted. Again, we arrived at the proper
desktop, but this time, when attempting to run the program, I received a
"DFRUN caused a stack problem in Conmode.dll at........." error message. That
occured all week, but we always maintained the correct desktop.
It was this past Friday, when working with our vendor to start a massive
upgrade to our software, that we noticed a different desktop, with games and
icons from my friend's kids about five years ago. That's where the mystery
lies. We don't want to boot from the D: drive, we just want to get back to
where we used to be on Thursday and every day before that. I can access all
the files on the D: drive, both through Windows Explorer and DOS. The
management software will be repaired tomorrow with Part 1 of the upgrade, but
where did an old desktop appear from?
--
Thank you for advice & ideas!
SteveG
"Don Phillipson" wrote:
> "SteveG" <SteveG@discussions.microsoft.com> wrote in message
> news:E9CA81AC-1610-493E-9BF3-9CB68C84731B@microsoft.com...
>
> > Here's what I forgot to add . . .
> >
> > The first thing I thought of was that somehow the BIOS got messed up. When
> > the machine booted (and still, boots) up, after the Windows 98 splash
> screen,
> > it drops to a DOS screen with lots of "REM-" lines. Years ago, when our
> first
> > machine crashed and I moved the drive over, I did set the new "D" drive as
> a
> > slave to the "C" drive in that computer.
> > So yesterday, I finally found out how to access this ancient machine's
> BIOS
> > (hit the "DEL" key at the eMachine splash screen) and re-directed the boot
> > order to the "D" drive, then re-booted the machine. The result? A "disk
> boot
> > failure."
>
> This is normal whenever a hard drive lacks "system code"
> -- cured by
> 1. DOS boot from floppy
> 2. command A:SYS D:
> which ought to write system code to the hard drive you
> use as D.
>
> This may create other problems: because bootable drives
> must be set by FDISK as "Primary DOS" partitions and
> Windows or DOS machines expect to find only one of
> these. The booting drive becomes C: and any other Primary
> DOS partition found becomes D. So when you boot from
> the master drive its partition becomes C: and when you
> boot from the slave or IDE2 drive it becomes C: and the
> master drive becomes D (and vice versa.)
>
> There seems no advantage in multi-boot options if both
> options are the same operating system (unlike say
> Windows/DOS and Linux.) Multiple differing desktop
> are configured by Windows via / Control Panel / Users
> as custom configurations for different users (selected
> by login name and password.)
>
> You may find it simpler to boot always from your master
> drive as C, and configure multiple users if needed. You
> do not need multiple sets of a solid OS that does everything
> you want (although a backup clone of C:/Windows may
> be useful -- see documentation at www.xxcopy.com.)
>
> (You also probably do not need AUTOEXEC.BAT and
> CONFIG.SYS, integral to Win95 but not used by Win98.
> Try renaming these so they do not run and see whether
> you reboot correctly and a bit faster.)
>
> --
> Don Phillipson
> Carlsbad Springs
> (Ottawa, Canada)
>
>
>
>