Can't boot win98! Sectors not found Dos error, right?

On 12/3/2010 20:11, Hot-Text wrote:


"Bill Blanton" wrote in message
ng.com...


If you resize, you have to adjust the FAT size. If FAT"16" then also
take into consideration the relative fixed location of the root dir
and move that. "In the way" file and dir clusters, immediately
following the FATs, have to be moved.,, You need to keep track of the
data clusters that are being moved so you can update the FAT's cluster
pointers. If your partition manager offers, and you accept to change
the cluster size along with everything else, then pray ;-)

It's not impossible of course, but whenever I want to resize a volume
I prefer to create a new empty volume and copy the files over, and/or
clone the volume before the resize. Of course many times you don't
have the luxury of that much space.

But create a new empty volume and clone the old volume to the new empty
volume is the Right Way to do it Always for Win98!

I don't know if "always", but under some circumstances.

"Bill Blanton" wrote in message
g.com...

I don't know if "always", but under some circumstances.


What circumstances?

On 12/3/2010 21:17, Hot-Text wrote:


"Bill Blanton" wrote in message
g.com...

I don't know if "always", but under some circumstances.


What circumstances?


resize vs. move

Bill Blanton I am Hot-Text
it was not me that ask What circumstances?

For if it was me I will say on a New HDD make two new empty volume, Put
Win98 in one Win2000 in Volume Two!
Go to http://gag.sourceforge.net/ and get GAG, THE GRAPHICAL BOOT MANAGER!



"Hot-Text" wrote in message
...


"Bill Blanton" wrote in message
g.com...

I don't know if "always", but under some circumstances.


What circumstances?

P.S.
You can make a Bigger volume and clone the old little volume in to it and
the Bigger volume will remain the same and windows 98, 2000 or XP
will run in the Bigger volume it work I do that all the time!

Have make made Two Bigger volume on one HDD and put (clone) the (98) old
little volume in to Big volume One (it add all the Free Space to it) and
made Big volume Two a Temp,
Then I Add a HDD with Two Bigger volume, In volume one I put (clone) the
(2000) old little volume in to it (and it add all the Free Space to it) and
made Big volume Two a Temp also,

Us THE GRAPHICAL BOOT MANAGER to boot it!
The Sec. HDD boot as if it was on C:

Bill Blanton wrote:
On 12/3/2010 00:43, PCR wrote:
PCR wrote:
John John - MVP wrote:


When Windows 98 is in a dual boot configuration with NT operating
systems you will run in the same problem if you resize the W9x
partition with just about any partition tool. This was pointed out
at the start of the other discussion thread, the problem is with
the Bootsect.dos file, this file becomes invalid if the DOS/W9x
partition is resized and it will then fail to boot properly.

When arranged in a dual boot configuration with NT operating
systems the W9x boot sector is copied to the Bootsect.dos file
then the NT boot sector is written to the partition. When you
boot the computer you boot using the NT boot sector which then
launches the Ntldr boot loader, if you select to boot Windows 98
ntldr will load the bootsect.dos file, which is a copy of the W9x
boot sector, being that the file was not updated when the
partition was resized it will fail, you need to rebuild this file
to reflect the changes in the partition.


What is it about Bootsect.dos that needs adjusting over a resize?
Has it grabbed the free space notation? A quick Google search shows
Bootsect.dos is mainly about IO.sys (to boot Win98),& that SYS will
restore it.


OK. This site...
http://thpc.info/dual/bootsequence.html
Boot Sequence in a Windows Dual-Boot Explained

...appears to have many answers. Everyone puzzling over a dual boot
should read it. It does state Bootsect.dos is "an image of the OS
Boot Sector Code for an OS other than XP/2K/NT", which is a PBR,&...

"A PBR, on a partition's first sector, contains a Parameter Block (or
Table) and some boot code.
The Parameter Block defines the characteristics of the partition
(size, sectors, file system, name, etc)."

So, size& number of sectors is in Bootsect.dos, which likely won't
get updated by resize. If those fields are used instead of
information that can be gleaned from the MBR or from the FAT (which
also I guess might not get updated by a resize) -- that does sound
like a problem with resize in a dual boot system. But I haven't seen
anyone run into the problem with BootItNG, that I can recall.

BootitNG has basic file edit capability inside its partition manager,
so it would have capability to update bootsect.dos. (if that's what it
does.. don't know)

Now, I've done a search. Looks like David &/or Pfeifer at BootItNG
solved the problem many versions ago...

http://www.terabyteunlimited.com/kb/article.php?id=088
Cannot Boot DOS/Win9x/Me After Resizing/Converting/Sliding/Copying a
FAT/FAT32 Partition that Uses WinNT/2K/XP Boot Manager
===Quote======
Starting with version 1.26e, the BOOTSECT.DOS file will be updated.
Other files which you may have (manually) captured and (manually) setup
to work with the ntldr will not be updated.
===EOQ=======


That site goes on to say...

"NTLDR loads the Bootsect file into memory and uses its OS Boot
Sector Code ... to boot the associated OS"

...,& not that it gets written back to the hard drive. I think it's
mainly looking for IO.sys& not for partition dimensions at this
point in the boot process. Earlier, the FAT must have gotten
involved; therefore, I still tend to think that's what Easeus missed.

The NT code in the volume boot sector will be loaded and those
"dimensions" used to ultimately find bootsect.dos. When bootsect.dos
loads it's pretty much a boot sector reset. The BPB inside
bootsect.dos is now used. There's no provision for the 9x code
(located inside bootsect.dos) to take into consideration any
parameters that NT may have set up.

The file is just poked into memory and jumped into just as if it was
in the boot sector. NT is finished at that point.

OK. I'll accept that now, & John was right too -- seeing as BootItNG
also had a problem with that once & Easeus still does -- that the size
values in Bootsect.dos are used; it isn't just needed for IO.sys! OK,
thanks.


--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR