Jump to content
MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. ×

Can there be Setup modification project? like 98Lite?


lama
 Share

PreSetup modification  

24 members have voted

  1. 1. Should there be nLite-like project to integrate/modify/update (official/unofficial files) into setup files?

    • Yes
      20
    • No
      9


Recommended Posts

Agreed. There was no such patch.

Well, I don't use Windows 95 OSR2.x but I do use the shell32.dll 4.00.1112 (From Windows 95 OSR2.x) under Win98SE, and it still mis-calculates the file sizes that are greater than 4GB....(The file size would wrap round at 4GB, hence this shows that MS had only made the SHELL32.DLL to use 32-bits)

I have no official OSR2 shell to test, but I maintain that the >4GB display problem goes away when I use the patched 95B shell. Did you try it?

Link to comment
Share on other sites


I have no official OSR2 shell to test, but I maintain that the >4GB display problem goes away when I use the patched 95B shell. Did you try it?

I think you misunderstood which dialog we were talking about. The 4GB display problem is not on the disk properties dialog (Which was fixed in 95B, but not the pie chart), but only occurs when you try to view the properties of a file>4GB(Not possible under Windows9x without using NTFS), or viewing >4GB worth of files.

The file sizes would "Wrap around" when it exceeds 4GB.

Also, I have used the patch uploaded by controller before (From Windows 95B QFE), and the problem was still there...

Edited by sp193
Link to comment
Share on other sites

...little silly problems such as the inability to properly size large directories...

I misunderstood. I rarely deal with such files; I view hdd free space a lot more often.

Edited by Session
Link to comment
Share on other sites

  • 3 weeks later...
When i talked about INF, I was hoping W98 setup would search for INFs (ICH7) at that detection moment (since right now, after setup reboots, I manually put those in INF folder)

There is a way to make it do this, but it's very poorly documented. "custom.inf", like msbatch.inf, is a "special" filename - if it exists in the setup directory, setup will automatically load it and copy the files it names to the locations it specifies.

custom.inf is designed for OEMs to preinstall drivers for hardware in the systems they make. It's been a while since I had to do stuff with it, but IIRC, it has two operative sections - the first, [Custom_Precopy], copies files to the temporary setup directory during the precopy phase; this guarantees that the driver infs will be seen during the initial hardware detection phase of setup. The second is a standard [baseWinOptions] section that can be used to copy files to the inf directory during the regular file copy phase (so the infs will be seen after the first reboot).

here's a skeleton custom.inf (nicked from intel's installer for my motherboard's chipset), with my annotations

[Version]
signature="$CHICAGO$"

[DestinationDirs]
; 2 is the temporary setup directory where the contents of precopy*.cab get expanded to before the actual filecopy phase starts. 17 is the normal inf folder.
PreCopyFiles=2 ; Windows temp setup directory
PreCatCopyFiles=2 ; Windows temp setup directory
InfCopyFiles=17 ; Windows \inf directory
CatCopyFiles=10,CATROOT ; Windows \CATROOT directory

;this section is automatically loaded and the copyfiles sections named in it are executed during the precopy phase.
; normally it's used to copy driver infs to the temporary setup directory
; since the registry doesn't exist during the precopy phase of setup, I doubt you can do much of anything else with it
[Custom_Precopy]
CopyFiles=PreCopyFiles
CopyFiles=PreCatCopyFiles

[PreCopyFiles]
foo.inf
bar.inf

;I don't know if you have to segregate cats from Infs like this unless you work for Intel
;I usually just delete the cat files and comment out references to them.
[PreCatCopyFiles]
foo.cat
bar.cat

; I have played with this section a little - you can use it to copy any files anywhere, not just infs.
; I haven't tried putting an "addreg" section here, since msbatch.inf works just fine for doing addreg stuff.
[BaseWinOptions]
InfCopy

[InfCopy]
CopyFiles=InfCopyFiles
CopyFiles=CatCopyFiles

[InfCopyFiles]
foo.inf
bar.inf

[CatCopyFiles]
foo.cat
bar.cat

;I once tried compressing the driver infs into a cab. I ran into problems,
;but I think it was because I had made a mistake somewhere.
[SourceDisksNames]
1="Intel Chipset", "", 0

[SourceDisksFiles]
foo.inf=1
bar.inf=1
foo.cat=1
bar.cat=1

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Recently Browsing   0 members

    No registered users viewing this page.


×
×
  • Create New...