[Sfor]

u2kforever, on Feb 28 2008, 06:09 PM, said:

So this thread is about, how you cant install a internal HD later then 137GB on WIN98SE

I was thinking about buying a HD , 160GB, i cant use it?

Please read,... then write.

This post has been edited by Sfor: 28 February 2008 - 02:59 PM

[Ponch]

Fredledingue, on Feb 28 2008, 10:47 AM, said:

Quote

Maybe holding the ctrl key down?

That was it! Many thanks! Actualy F8 let me choose the boot drive (floppy, HD, CD-rom etc). .

Then it's hardware managed, before the OS boots.
+booting DOS 6 in safe mode was achieved by the Ctrl key, maybe not for Win98.

[Fredledingue]

Of course it's hardware managed (before OS boots). How else?

[WJCR]

There's no reason why this hard drive couldn't be used in Windows 98 SE, is there?

http://www.walmart.c...duct_id=4898004

[galahs]

yep, it should work.

Just as soon as you install Win98SE install LLXX's 2225 patch or Gapes Unofficial Service Pack 3 beta 1




Personally I'd divide it into at least 2 partitions, each no partition bigger than 120GB (you still need the patches though)

This post has been edited by galahs: 05 March 2008 - 07:23 PM

[Fredledingue]

Excellent tutorial on how to use FDISK:

http://fdisk.radified.com/

(if it's your first time, you definetely have to read it)

As I can see the catch is, finaly, to get a suitable bootable floppy with the updated files either by downloading the M$ Q311561 patch here before creating your boot floppy (then if you want, re-apply MDGx's BHDD30 update) or by downloading BOOT98SC.EXE from bootdisk.com and replace the files but the ME version should work, since updated files are from ME.

During the w98 installation, when the installer reboot, you have to press F8 (or Ctrl on some computers) and reboot in DOS. Then replace the files (both those from the 48BitLBA - Break 137Gb barrier - patch and from BHDD30.zip.) to avoid system crash or other problems.
You must also replace scandisk.exe from MDGx's package SCANFRAG (Thanks Dencorso for this info).

To facilitate this task I wrote a batch script. Instead of typing every command one by one, just type the location and name of the bat file containing htis code.

This script works if all the files are located in the same directory as that of the bat file. The source directory not being coded in. You must pick the files manualy from an updated system and copy them to the directory where you will place the batch script.
Before gathering all the files from theirs Windows locations you must have applied all these patches (already mentioned above):
Q311561
BHDD30
48BitLBA
SCANFRAG

It will aslo open system.ini to allow you the make the changes for more than 512Mb of memory.

Code Updated 8th July 2008

@echo off

   echo Support for hard discs larger than 125Gb
move C:\WINDOWS\SYSTEM\IOSUBSYS\ESDI_506.PDR C:\WINDOWS\SYSTEM\IOSUBSYS\ESDI_506.OLD
copy ESDI_506.PDR C:\WINDOWS\SYSTEM\IOSUBSYS\ESDI_506.PDR

move C:\WINDOWS\SYSTEM\VMM32\IOS.VXD C:\WINDOWS\SYSTEM\VMM32\IOS.old
copy IOS.VXD C:\WINDOWS\SYSTEM\VMM32\IOS.VXD

attrib -s -h -r IO.SYS 
move C:\IO.SYS C:\IO.old
copy IO.SYS C:\IO.SYS
attrib +s +h +r IO.SYS

move C:\WINDOWS\OPTIONS\CABS\SCANDSKW.EXE C:\WINDOWS\OPTIONS\CABS\SCANDSKW.old
copy SCANDSKW.EXE C:\WINDOWS\OPTIONS\CABS\SCANDSKW.EXE
move C:\WINDOWS\SCANDSKW.EXE C:\WINDOWS\SCANDSKW.old
copy SCANDSKW.EXE C:\WINDOWS\SCANDSKW.EXE

move C:\WINDOWS\OPTIONS\CABS\DSKMAINT.DLL C:\WINDOWS\OPTIONS\CABS\DSKMAINT.old
copy DSKMAINT.DLL C:\WINDOWS\OPTIONS\CABS\DSKMAINT.DLL
move C:\WINDOWS\System\DSKMAINT.DLL C:\WINDOWS\System\DSKMAINT.old
copy DSKMAINT.DLL C:\WINDOWS\OPTIONS\CABS\DSKMAINT.DLL

move C:\WINDOWS\OPTIONS\CABS\DSKMAINT.DLL C:\WINDOWS\OPTIONS\CABS\DSKMAINT.old
copy DSKMAINT.DLL C:\WINDOWS\OPTIONS\CABS\DSKMAINT.DLL
move C:\WINDOWS\System\DSKMAINT.DLL C:\WINDOWS\System\DSKMAINT.old
copy DSKMAINT.DLL C:\WINDOWS\System\DSKMAINT.DLL

move C:\WINDOWS\OPTIONS\CABS\DEFRAG.EXE C:\WINDOWS\OPTIONS\CABS\DEFRAG.old
copy DEFRAG.EXE C:\WINDOWS\OPTIONS\CABS\DEFRAG.EXE
move C:\WINDOWS\DEFRAG.EXE C:\WINDOWS\DEFRAG.old
copy DEFRAG.EXE C:\WINDOWS\DEFRAG.EXE

move C:\WINDOWS\OPTIONS\CABS\CVTAPLOG.EXE C:\WINDOWS\OPTIONS\CABS\CVTAPLOG.old
copy CVTAPLOG.EXE C:\WINDOWS\OPTIONS\CABS\CVTAPLOG.EXE
move C:\WINDOWS\CVTAPLOG.EXE C:\WINDOWS\CVTAPLOG.old
copy CVTAPLOG.EXE C:\WINDOWS\CVTAPLOG.EXE

move C:\WINDOWS\COMMAND\FORMAT.COM C:\WINDOWS\COMMAND\FORMAT.old
copy FORMAT.COM C:\WINDOWS\COMMAND\FORMAT.COM

move C:\WINDOWS\COMMAND\EBD\FDISK.EXE C:\WINDOWS\COMMAND\EBD\FDISK.old
copy FDISK.EXE C:\WINDOWS\COMMAND\EBD\FDISK.EXE
move C:\WINDOWS\COMMAND\fdisk.exe C:\WINDOWS\COMMAND\fdisk.old
copy FDISK.EXE C:\WINDOWS\COMMAND\fdisk.exe

move C:\WINDOWS\SYSTEM\ADVPACK.DLL C:\WINDOWS\SYSTEM\ADVPACK.old
copy ADVPACK.DLL C:\WINDOWS\SYSTEM\ADVPACK.DLL

move C:\WINDOWS\SYSTEM\W95INF32.DLL C:\WINDOWS\SYSTEM\W95INF32.old
copy W95INF32.DLL C:\WINDOWS\SYSTEM\W95INF32.DLL

move C:\WINDOWS\COMMAND\SCANDISK.EXE C:\WINDOWS\COMMAND\SCANDISK.old
copy SCANDISK.EXE C:\WINDOWS\COMMAND\SCANDISK.EXE
move C:\WINDOWS\SCANDISK.EXE C:\WINDOWS\SCANDISK.old
copy SCANDISK.EXE C:\WINDOWS\SCANDISK.EXE

edit  C:\WINDOWS\SYSTEM.INI

Any comment?

This post has been edited by Fredledingue: 09 July 2008 - 09:39 AM

[dencorso]

Fredledingue, on Jun 21 2008, 05:46 PM, said:

Any comment?

Yes. Two. I'm sure you know this already, but just for the sake of future readers of this topic:
(1) The IOS.VXD one should use is 4.10.2225 and is findable inside Gape's Unofficial Service Pack or inside Q239696.
(2) The LLXX's patched ESDI_506.PDR that one should use is 4.10.2225, unless one has an IBM Laptop.

And, BTW, great post: I'm sure it'll be of help for many users. You rock!

PS: It's also a good idea to remind the reader that the IO.SYS from Q311561 (which you alreadey had given a pointer to) must be installed also to the HDD, not just to the floppy bootdisk. Of course it'll end there if the floppy is used to format/s the HDD. But perhaps your batch might install it to both the root dir and c:\windows\command\EBD, just in case. And since it is named winboot.98s inside Q311561, you'll need to rename it to IO.SYS, before doing the copies.

This post has been edited by dencorso: 21 June 2008 - 10:24 PM

[Fredledingue]

dencorso,
Q311561.exe is an installer, I can't etract individual files via batch script.
My IO.SYS on my root drive at the moment dates from dec 2001. Is it the latest updated version?

[jaclaz]

Fredledingue, on Jun 22 2008, 11:09 AM, said:

dencorso,
Q311561.exe is an installer, I can't etract individual files via batch script.
My IO.SYS on my root drive at the moment dates from dec 2001. Is it the latest updated version?

I had a quick look to:
311561usa8.exe

For the record, it appears to be a CAB self-extracting archive, with a stub of 67224 bytes.

Search in it with a hex editor, for "PMSCF" the "P" is the last byte of the stub, "MSCF" is the header of the CAB.

Once you remove the first 67224 (and possibly change the extension to CAB), it should be uncompressable with "normal" EXTRACT.EXE. (did not test personally)

Contents are these:

01/12/2001  11.06				1.368 1998UN.INF
01/12/2001  11.03				1.378 2222UN.INF
01/12/2001  10.55				  765 311561UP.INF
01/12/2001  11.01				2.568 98G_chk.INF
03/12/2001  12.47				2.572 98SE_chk.INF
11/12/1997  05.33			   80.864 ADVPACK.DLL
12/08/1998  20.32			   16.896 csetup.exe
27/07/1998  14.48			   36.864 qfecheck.exe
09/02/1996  17.28				8.042 qfecheck.hlp
04/12/1997  12.02				2.272 W95INF16.DLL
04/12/1997  12.02				4.608 W95INF32.DLL
30/11/2001  15.31			  222.670 winboot.98g
01/12/2001  09.37			  222.670 winboot.98s

The two winboot.98x should be IO.SYS renamed for Gold and SE.

jaclaz

[Fredledingue]

I'm not sure if I will include IO.SYS because it's supposed to be created during disk formating and also because I'm not sure it's possible to replace it even in DOS without error or that it's safe to do that.

Note: If you face the "Drive running in DOS compatibility mode" issue after applying LLXX's ESDI_506.PDR version 4.10.2225, then use version 4.10.2222.

Note: batch script updated! (Added: Fdisk.exe)

[dencorso]

Fredledingue, on Jun 22 2008, 06:09 AM, said:

dencorso,
Q311561.exe is an installer, I can't etract individual files via batch script.
My IO.SYS on my root drive at the moment dates from dec 2001. Is it the latest updated version?

Yes, it is! There are two versions of Win 98SE IO.SYS:
IO.SYS 222390 04/23/1999 22:22 (Win 98SE original)
IO.SYS 222670 12/01/2001 09:37 (Win 98SE Q311561)

In fact, a short time ago, jaclaz found out there exists a further (unofficial) patch to the Q311561 IO.SYS, but for the moment I'm not recomending it, until I can give a closer look into it, to convince myself it's safe and works OK, which I'm meaning to do as soon as I get enough time for it. You can find out more about it here: Patched-IOSYS-for-98SE-and-ME

As for extracting individual files from Q311561 (and from Q239696) you can do it simply by opening them inside WinRAR or 7-Zip. It's easier than what jaclaz proposed above, but requires that you have access to a second machine, already running any Windows, from 95A to Vista (or Linux). I don't know any DOS program able to do it directly, however, sorry! My idea was simply to start the batch using previously extracted files...

BTW, provided you have booted the system from a different disk from the one in which you intend to replece the IO.SYS, I'm positive it is safe to do it in DOS mode. You can rename IO.SYS to, say, IO.OLD and add the new IO.SYS. It'll work fine, from Win 95 up to Win ME (DOS 7.00 to 8.00). This is not true, however, for DOS 6.22 or any earlier version (they required that IO.SYS and MSDOS.SYS be physically the first and second files in the disk, respectively, and also that their directory entries be the first and second entries, respectively, or else would refuse to boot... but that's in the past already, isn't it?).

This post has been edited by dencorso: 22 June 2008 - 05:32 PM

[jaclaz]

@dencorso

From batch, you use a DOS file splitter, like PARTCOPY:
http://web.archive.org/web/20010116021600/...ine/pcopy02.zip
(courtesy of the Wayback Machine)

or a similar one, to make a file from the bytes starting from byte 67224 (or use GSAR to find occurence of "MSCF"), then run EXTRACT.EXE on the partial "tail" file.

Not exactly starightforward, but allows for doing everything on a DOS machine.

jaclaz

[Fredledingue]

The easiest way to "extracting the file" is still to apply the patches and pick the files manualy.

The idea is that you have already w98 running (either on the same machine or on another one), then it make sens to apply all the patches.
If you don't, let's say you have only an XP computer and you have another computer without anything or you want to downgrade an XP cmputer to w98, in this case you can try different methods for extracting the files. But even easier would be that I upload the files on my website.

Note: batch script updated! (Added: io.sys)

This post has been edited by Fredledingue: 23 June 2008 - 08:37 AM

[jaclaz]

@Fredledingue

I had taken this:

Fredledingue, on Jun 22 2008, 11:09 AM, said:

Q311561.exe is an installer, I can't etract individual files via batch script.

as:
"it's impossible to extract individual files from batch script"

and just wanted to let you know that it is actually possible.

Fredledingue, on Jun 23 2008, 04:33 PM, said:

But even easier would be that I upload the files on my website.

Definitely easier.

jaclaz

[Fredledingue]

If you have Nero, you can create a copy of the boot floppy on CD and the CD will act as a bootable disc.
To do that: insert the bootable floppy into its drive, open Nero, create "new", select CD (Boot), save, insert a blank CD-rom and burn. While burning Nero reads the datas from the floppy and copy them on the CD.

[dencorso]

@jaclaz: PARTCOPY and GSAR! I didn't know either... great findings, jaclaz, great findings! Thanks a lot!

@Fredledingue: I think the SCANFRAG update adds too much things to the system, in addition to the needed SCANDISK.EXE, so I seached some more and I just found an alternative source for it: the Win ME OEM bootdisk available at bootdisk.com (link)... instead of applying SCANFRAG just create the boot diskette and open the EBD.CAB it contains and extract the Win ME DOS SCANDISK.EXE from inside it. If, however, you decide to apply SCANFRAG, do it first and then apply BHDD30, in this order, just to remain on the safe side, because the dskmaint.dll in SCANFRAG is from Win 98, while the dskmaint.dll in BHDD30 is from Win ME (the one that must be used).

You both rock!

[98-Guy]

Cluster size and exploring the limits of FAT-32

http://groups.google.com/group/microsoft.p...f15325586abfa68

or try this:

http://tinyurl.com/4dxdcz

------------------

Windows 98 large file-count tests on large volume (500 gb hard drive)

http://tinyurl.com/3p285h

[Fredledingue]

Thanks for these valuable informations, 98-Guy!
This confirm and precise what we have been talking or speculating about.

[Fredledingue]

I talked a lot, and it was time to walk the talk...

I installed w98se on a 400Gb had disk, on a 38Gb partition on it, with another 345 Gb partition left for multimedia stuffs.
I still have the old hdd, with the full installation still intact, which is very useful.

The funny thing is that the two partitions/drive letters of the hard disk are saddled on the old disk drive letter:
C :, D:, E
C and E belong to a same physical hard disk and D belongs to another one. Not very important, just to say that it can happen.

First thing I have learned is: Do not use ME Bootdisk-Custom from bootdisk.com: It failed to porperly delete old partitions causing a hell of troubles. (full story here)

After I realised that, I used fdisk and format from BHDD30.zip and it worked.
Maybe other bootdisks from bootdisk.com work, I didn't test them.

Then more problems!
When launching windows setup I got this:

Please wait while Setup initializes
Scanning system registry...
Copying files needed for Windows Setup...

and then nothing happened.

==> I solved this problem by rebooting via floppy boot disk (original) in "Safe mode command prompt only".
Then he accpeted to install windows.

During restart, after the installer had copied all files, I pressed Ctrl and rebooted in dos mode to replace all files for supporting big hard drives, and to edit system.ini to support more than 512 Mb of memory.

For that I used the batch script above.
To my susprise, several files couldn't be copied because the location didn't existed yet or were not present in the directory where the bat file was.
The latter is very surprising, but ok.
Very cool was the edit command to add entries into system.ini.

Unfortunately, Windows didn't want to start:

Windows protection error.

Pffft...!
That's the worse error you can have because you can't load in safe mode.

==> The reason? IO.SYS had not been replaced by the bat script. In fact it cannot be replaced in plain Dos mode. That's maybe the only file on the whole system which can be deleted/replaced under windows but not under Dos.
So, I reset the jumpers and the ribbon cables to get back to the old hardware configuration and restarted on the old hard drive. Then, I replaced IO.sys on the new drive, simply with windows explorer. (full story here)

The question is: How to do without a second drive (<137 Gb) with windows already installed? I don't know, but I'v read that such error is rather rare.
I hope I'v got all the "rare" errors here.

Maybe a bad IO.sys on the boot floppy was also the reason why setup didn't start at first?

Hah! Sometimes I think that XP and Vista users are lucky ones!

[dencorso]

Hi, Fredledingue!
Sorry, it's my bad... I forgot to mention that you need to change IO.SYS attributes before being able to replace it in DOS mode, AND did not recheck your batch file for it. So, let's spell it here:

1) run ATTRIB IO.SYS from the root directory and you'll see:
SHR IO.SYS C:\IO.SYS
...this means that IO.SYS has the System, Hidden and Read-only attributes

2) now run ATTRIB -s -h -r IO.SYS from the root directory

3) run again ATTRIB IO.SYS from the root directory and you'll see:
IO.SYS C:\IO.SYS
...this means that IO.SYS now has no attributes

4) replace IO.SYS

5) now run ATTRIB +s +h +r IO.SYS from the root directory

6) run again ATTRIB IO.SYS from the root directory and you'll see:
SHR IO.SYS C:\IO.SYS
...this means that IO.SYS has again the System, Hidden and Read-only attributes

Of course, you only need to add to the batch file step (2) before replacing IO.SYS and step (5) after it.
It also means that you need to have ATTRIB.EXE present in the directory from which the batch file is run.

Sorry. I've performed the substitution of IO.SYS from plain DOS so many times already that I forgot to mention you need to change the attributes, and then change them back... But it can be done from DOS, and it can be done with a batch file. Windows Explorer doesn't care much about the DOS file-attributes, but DOE does care.

In what regards the attribution of the drive letters, DOS will give C: to the active primary partition in the first physical disk, then D: to the active primary partition in the second physical disk, then give the next letters to all drives in the extended partition of the first physical drive, then to those in the second physical drive (and then give letters to any inactive additonal primary partitions present in the first, then the second physical drives, in this order, when they exist).

This post has been edited by dencorso: 08 July 2008 - 07:14 PM