Dual boot, boot mode previous DOS, 2nd partition hangs

[edfair]

Intention is to have 95a/DOS 6.22, 98SE/DOS 6.22, and ME as 3 partitions choosing under boot magic. Ran this way for at least a year with P100 , but have recently upgraded to P200. (maybe a better word would be changed)
Loaded the 2nd partition on active,visible partition with DOS then a hard drive install of SE and enabled BootMenu=1 in msdos.sys.
System starts, IO.sys gives the choice, I choose #7 (previous OS) ,get a message that system is booting with the previous version and it hangs with hard drive accessing.

Have loaded partition 1 with DOS/SE and compared the system files looking for corruption or differences, but can't find any. Partition 1 boots either as expected when active or under boot magic. Partition 2 loads SE but fails on 6.22.

Anybody have any insight to what I may have overlooked?

Ed Fair
Any advice I give is my best judgement based on my interpretation of the facts you supply. Help increase my knowledge by providing some feedback, good or bad, on any advice I have given.

 

[TekTippy4U]

I probably shouldn't even try to touch this one with a
ten-foot pole.......but what the hey......miles and miles of cable between us.....:>).....

In the hopes of being somewhat useful in helping others.... here it goes

What do you have entered for BootWin=
...if you even have it listed in msdos.sys.....
What does your whole dos.sys file say?.....

 

[wolluf]

Ed - have you tried the old 'just set it up again & see if it works this time' yet?

 

[edfair]

TT4u
I'll look tonight and post back.

Wolluf,
Oh, yes. Multiple times. Failure is also on 3rd partition. Because of the 98 troubleshooting I have 3 identical partitions set up identically. I'll wipe away and get 95 & ME later.
I've been doing the dual boot thing since 95 and had it down pat. And now it fails over a board change. But it won't fail on the front end partition. That bugs me.

Ed Fair
Any advice I give is my best judgement based on my interpretation of the facts you supply. Help increase my knowledge by providing some feedback, good or bad, on any advice I have given.

 

[wolluf]

So you've got 3 identical primary partitions? Have you tried setting them up in reverse order? (hide 1&2, setup 3, etc). Can't see why it would make a difference - but can't see (like you) why its not working anyway.

 

[TekTippy4U]

Let me just give you an idea of where I was going with this one.........so you may be able to eliminate it as an issue before tonight...
BootWin=1....enables win 98 as the default OS...when set..
BootWin=0...disables win 98 as default,....this function is only useful with ms-dos versions 5 or 6.xx..on the box....

I understood from your original post that Partition 2....was giving you a problem in getting to Dos.....

You say the hard disk just spins.....could it be
AutoScan=2...is there in msdos.sys....as this will automatically launch scandisk at startup...
AutoScan=0......disables this...
AutoScan=1....gives a prompt before starting.....but will kick in on it's own in 1 min. if not responded to.....

Here's a clip from a book I got....concerning 98 and older dos versions;
Tip for Starting an Earlier Version of MS-DOS
If you installed Windows 98 in its own directory, the earlier version of MS-DOS is preserved on your hard disk. If you set BootMulti=1 in the [Options] section in the Windows 98 version of Msdos.sys, you can start the earlier version of MS-DOS by pressing F4 when the Starting Windows message appears during system startup
(you're probably well aware of this)

Now from your recent post, I see that partition 2 and 3 appear to have the issues....

From another perspective....one can't help think that it must have something to do with the new mobo you've installed.....can you give more info on that?.......I thought you meant just a new CPU at first.....( silly me).....The new mobo means new BIOS....correct?....so maybe the formatting isn't going as expected..

Don't know if any of this helps....but I've seen you give some good advice in other threads and would really like to see you up and running, the way you like.....
Hopefully, some others will weigh in with more exp. on this......I'll keep reading though..to see what, if anything, I can come up with......

Peace

 

[edfair]

ttfu,
I'm up and running on all that I really need, these just happen to be 2 additional partitions on another machine that I sometimes use as a testbed for loading something.
The M/B is Gigabyte with intel PXII chipset, which is one of the problem chipsets for 95, but not for 98. DOS loads the same way in all 3 partitions and is working fine on each partition prior to the 98 load. And at this time I'm not involving the bootmanager, just change the active partition with partition manager to bring up a different one. I boot to dos and run setup from the 98setup directory.
98 installs the same, goes through the same gyrations and reboots and when is all said and done SE works the same on all partitions. Then the line change in msdos.sys to give boot menu. Reboot and partition 1 gives access to all with no problems, partitions 2 & 3 are OK with everything except previous DOS. There the hard drive keeps accessing something and proceeds no further. Something like a crosslink to itself, but that isn't indicated.

Ed Fair
Any advice I give is my best judgement based on my interpretation of the facts you supply. Help increase my knowledge by providing some feedback, good or bad, on any advice I have given.

 

[TekTippy4U]

Do you have a "Setver" line for dos 6.22 in config.sys?........(maybe a TSR problem?)
and is Win98 SE installed in it's own directory?

 

[edfair]

All file names are from DOS6.22 to prevent confusion due to the windows renaming conventions
In order with some additional details:
SE is in w98 on both partitions
Msdos contains:
paths wdir=c:\w98 boot=c:\98 host=c
multi=1 gui=1 menu=1 dblbuf=1 scan=1 ver=4.10.222
there is no bootwin entry

At the beginning there are the 3 msdos files
io.sys, msdos.sys and command.com ,himem and emm both active but the config& autoexec were removed for 98 install

after first part of install the 3 DOS files end with .dos and new msdos.sys io.sys and command.com are in place

the next part of install adds the progra~1 directory

the next part finds monitor and adds mydocu~1

on next boot into 98 I edit msdos.sys to add boot menu and reboot

I go with a DOS floppy to see the files and find that the
previous 98 files become JO.sys msdos.w40 and command.w40
and the DOS files become io.sys, msdos.sys and command.com

both partitions have identical file names and identical content on all system files. Partition 1 boots to dos, partition 2 processes jo.sys but hangs, never getting into io.sys.
Agree , it is probably the board. But I'm a tech and supposed to be able to find the answer.



Ed Fair
Any advice I give is my best judgement based on my interpretation of the facts you supply. Help increase my knowledge by providing some feedback, good or bad, on any advice I have given.

 

[TekTippy4U]

Just a few thoughts edfair;
I hope I'm not misinterpreting the info you've posted;

In reference to the text below...you may have to put entries in Config.sys......that win98 Io.sys(contains)... and removed from config.sys during setup of win98.....for compatibility with the older dos

The values in Io.sys cannot be edited. If Config.sys contains switches or other parameters for any of the drivers or settings created by Io.sys, the Config.sys entries "override" the Io.sys defaults.....(I have the defaults if necessary)
(Io.sys does not load EMM386.)

dos=high
Specifies that MS-DOS should be loaded in the high-memory area (HMA).

Also, the "UMB" value is included if EMM386 is loaded from Config.sys..........

Maybe........in config.sys.....example...
Device=c:\win98\himem.sys
Device=c:\win98\emm386.exe

which Should Add a.......

Dos=high,umb...right beneath the above lines

Don't know if this helps....as I've only used other partitions for storage purposes...as Extended-dos......not Multi-boot.....per se..

 

[edfair]

Once DOS boots and before I run 98 setup I rename the autoexec.bat and config.sys to .org. 9x use the AE and Config from dos to build their own AE and config so by renaming I get AE and config of 0 length. I don't need anything loaded and can run with the defaults.
Then once DOS will boot to minimal I rename the .org back to the right names and reboot to DOS and have recovered.
At this point I have AE.bat and AE.w40, config.sys and config.w40 (DOS 6.22 names), the w40 both empty.

Ed Fair
Any advice I give is my best judgement based on my interpretation of the facts you supply. Help increase my knowledge by providing some feedback, good or bad, on any advice I have given.

 

[TekTippy4U]

I am really at a loss here edfair......your configuration is probably a great proven way to do it as I have little to none exp. with DOS......

I sincerely hope you resolve this issue......and possibly with other list members' help.......

I'll keep scratchin'.....and trying to follow along

p.s....would love to know the answer of problem when resolved..

Peace

 

[AirCon]

edfair,

I'm beginning to see the problem. I experienced this once but still I need to clarify first.

The problem you have now is, you can boot to previous version but you can't boot into W98SE on 2nd partition isn't it ?


-- AirCon --

 

[TekTippy4U]

After carefully rereading ( I hope)..and trying to understand.....I don't think renaming AE and Config to .org....when installing 98 (I guess to fool it).....isn't the way to go....(I really don't know, edfair)....

Remember I said in an earlier post here Win98 needs to be in it's own directory?......This may have something to do also with the need to call it's own Io.sys file (as you know contain a comb. of;

dos=high himem.sys ifshlp.sys setver.exe files= lastdrive= buffers= stacks= shell=command.com /p"?" fcbs= ......when booting......

Entries for files=, buffers=, and stacks= must be set in Config.sys to at least the default values in Io.sys. Maybe in old dos 6.22 they're not?....
...when booting......so if you allow it to do that...and then just readd those entries for older dos in config.sys......just maybe that'll help.....again.....just a hunch...

I don't know how Dblspace.bin,.....vxd, even work, but I know they're needed.....here's
-A snipit of text-
Windows 98 automatically unloads any real-mode drivers for which it has protected-mode drivers to provide the same functionality. For example, the real-mode Dblspace.bin driver is unloaded, and the protected-mode Dblspace driver, Drvspacx.vxd, takes over. However, the protected-mode device driver should take over only when it guarantees functionality similar to that of the real-mode driver, not merely because it can drive the hardware

Again I really don't know if I'm confusing you more than I already am...I hope not.....Just ignore this stuff if it sounds like jabberwocky after reading.......
Peace

 

[vbrocks]

Is it possible that dos 6.22 does not recognize your FAT32 Partitions?

 

[edfair]

AirCon, I can't boot to previous version on 2nd partition but Se is OK.

TT4u, SE is in its own directory. Named w95 to distinguish it from 3.1 which may or may not be in \w31. In this case 3.1 hasn't been loaded yet to keep the problem simple.

vbrocks, both partitions are FAT16 < 600mb.

Thanks for replies, I'll use the suggestions when I can. I've got a unix system calling for me.

Ed Fair
Any advice I give is my best judgement based on my interpretation of the facts you supply. Help increase my knowledge by providing some feedback, good or bad, on any advice I have given.

 

[edfair]

TT4u,
Partition that works has no compression drivers (dbl or drvspace). Partition that fails has both. And the hard drive accesses evidently is related to one of them since the accesses stop as soon as the files are removed. DOS boot hangs at &quot;loading previous version&quot; but no continuous drive activity.
Time to reload SE without the compression drivers being available and see what happens.
Later.

Ed Fair
Any advice I give is my best judgement based on my interpretation of the facts you supply. Help increase my knowledge by providing some feedback, good or bad, on any advice I have given.

 

[TekTippy4U]

One more quick thought....have you tried a /p switch in Command.com to maintain it......
By default, the /p switch is included to indicate that the command process is permanent and should not be unloaded. If the /p switch is not specified, Autoexec.bat is not processed and the command process can be unloaded when quitting the operating system.

 

[AirCon]

Arrgghhh.. you had mentioned that the system failed on 6.22 (I am sooo.. stupid :-D )

Ok, I'm not so sure yet (it's been years since I the last time I played with DOS 6.22), but I think the problem here is the previous DOS file extension must be DOS, not W40. And IO.SYS must be named IO.DOS instead of JO.SYS

Also could you check the filesize of jo.sys, msdos.w40 and command.w40 ?
Is it the same size with io.sys, msdos.sys and command.com ?


-- AirCon --

 

[edfair]

AirCon,
At the intermediate steps the DOS stuff is *.dos and the SE files take over the normal names. At the bootmenu change the DOS versions change back to *.sys and command.com and the 98 names which were io.sys msdos.sys and command.com become JO.sys msdos.w40 and command.w40. I haven't figured out yet exactly when the change takes place, but I'm working on it.
windows versions dos versions
IO 222K 40K
msdos 1668 38K
command 93K 54K
and the sizes remain the same except for msdos.w40 which adds size to reflect the bootmenu=1 line.

Ed Fair
Any advice I give is my best judgement based on my interpretation of the facts you supply. Help increase my knowledge by providing some feedback, good or bad, on any advice I have given.