BetaArchive Logo
Navigation Home Screenshots Image Uploader Server Info FTP Servers Wiki Forum RSS Feed Rules Please Donate
UP: 28d, 8h, 19m | CPU: 40% | MEM: 5948MB of 12227MB used
{The community for beta collectors}

Post new topic Reply to topic  [ 17 posts ] 
Author Message
 PostPost subject: Newest Whistler build that won't make me have 64mb of RAM        Posted: Thu Sep 13, 2007 10:46 am 
Reply with quote
FTP Access
Offline

Joined
Thu Sep 13, 2007 3:24 pm

Posts
38

Favourite OS
Mac OS X 10.7
I'm currently running Microsoft Neptune Build 5111 on my other computer. It did not force me to have 64 MB of RAM and let me install. I have Whistler Build 2201. I have not tried much to install it because I don't know if it's any better than Neptune Build 5111. I have Whistler Build 2419, but I can't install it because it says I have to have 64 MB of RAM. What's the newest Whistler build that won't force me to have 64 MB of RAM? And where can I find it?


Top  Profile  WWW
 PostPost subject:        Posted: Thu Sep 13, 2007 11:01 am 
Reply with quote
Donator
Offline

Joined
Fri Aug 18, 2006 12:05 pm

Posts
698

Location
Or-stray-liagh
I'm not sure exactly which build it is ... however, if you're willing to change a few files in the ISO you can get rid of the memory requirement in any build using software like nLite. As far as I know it should work, nLite will probably see the ISO as a copy of either Windows XP or 2000.

_________________
pr0gram the pr0grammer
BetaArchive retiree | OSBA Expat


Top  Profile
 PostPost subject:        Posted: Thu Sep 13, 2007 11:04 am 
Reply with quote
FTP Access
Offline

Joined
Thu Sep 13, 2007 3:24 pm

Posts
38

Favourite OS
Mac OS X 10.7
pr0gram the pr0grammer wrote:
I'm not sure exactly which build it is ... however, if you're willing to change a few files in the ISO you can get rid of the memory requirement in any build using software like nLite. As far as I know it should work, nLite will probably see the ISO as a copy of either Windows XP or 2000.

Is there any way I can modify it manually? Or find for download every known Whistler build? (perhaps I could just try using a really early build, but it must contain the watercolor theme)


Top  Profile  WWW
 PostPost subject:        Posted: Thu Sep 13, 2007 11:07 am 
Reply with quote
Donator
User avatar
Offline

Joined
Sat Aug 19, 2006 12:19 am

Posts
1915

Location
New Zealand
just use nlite, it would be much easier. i think its under the tweak section


Top  Profile
 PostPost subject:        Posted: Thu Sep 13, 2007 11:25 am 
Reply with quote
If you don't want to use nlite, or if it doesn't work with your whistler build,
you could try the following:

1. open TXTSETUP.SIF with a text edtor (it is just a huge text file)
2. search for "RequiredMemory". You will find an entry like:
RequiredMemory = 67108864
3. change this entry to fit your needs.
4. save the file

Alternatively, if you want to burn a CD with your modified ISO image, you could use a hex editor and locate the "RequiredMemory" entry directly inside the ISO for editing (that way you don't have to extract TXTSETUP.SIF and build a new ISO after editing).


Top
 PostPost subject:        Posted: Thu Sep 13, 2007 11:44 am 
Reply with quote
Donator
Offline

Joined
Sat Sep 30, 2006 5:00 pm

Posts
3557
I think all non-server builds from the 22xx range should install on less than 64MB RAM, as does Windows 2000 Pro.


Last edited by empireum on Thu Sep 13, 2007 5:49 pm, edited 1 time in total.

Top  Profile
 PostPost subject:        Posted: Thu Sep 13, 2007 12:11 pm 
Reply with quote
Quote:
What's the newest Whistler build that won't force me to have 64 MB of RAM?

That's exactly the problem of the thread starter...


Top
 PostPost subject:        Posted: Thu Sep 13, 2007 12:53 pm 
Reply with quote
FTP Access
Offline

Joined
Thu Sep 13, 2007 3:24 pm

Posts
38

Favourite OS
Mac OS X 10.7
boxmaker wrote:
If you don't want to use nlite, or if it doesn't work with your whistler build,
you could try the following:

1. open TXTSETUP.SIF with a text edtor (it is just a huge text file)
2. search for "RequiredMemory". You will find an entry like:
RequiredMemory = 67108864
3. change this entry to fit your needs.
4. save the file

Alternatively, if you want to burn a CD with your modified ISO image, you could use a hex editor and locate the "RequiredMemory" entry directly inside the ISO for editing (that way you don't have to extract TXTSETUP.SIF and build a new ISO after editing).

I did this, and it STILL says I need 64. :(


Top  Profile  WWW
 PostPost subject:        Posted: Thu Sep 13, 2007 1:22 pm 
Reply with quote
I'm sorry. I remeber having done it that way back in 2001 (even with newer whistler builds which had luna). They installed OK with 32 MB RAM. So there was a way to get it to install.

I may have forgotten some other entries that need a change. I will check this and see if I find my old solution again! May take an hour or two...

BTW, have you started the install from within windows, or by booting from the CD?


Top
 PostPost subject:        Posted: Thu Sep 13, 2007 1:26 pm 
Reply with quote
The minimum ram requirement is also listed in the dosnet.inf from memory.


Top
 PostPost subject:        Posted: Thu Sep 13, 2007 1:41 pm 
Reply with quote
Thanks Unknown. I've just confirmed this using build 2296 and a virtual PC with 32 MB RAM. Back in 2001 it still worked with XP final, so I'm quite sure that build 2419 will also install.

Updated instructions:

1. open TXTSETUP.SIF with a text editor (it is just a huge text file)
2. search for "RequiredMemory"
3. change this entry to fit your needs.
4. save the file
5. open DOSNET.INF and do the same with "MinimumMemory"

Still I would recommend in-ISO hex editing to keep a bootable CD...


Top
 PostPost subject:        Posted: Thu Sep 13, 2007 2:52 pm 
Reply with quote
FTP Access
Offline

Joined
Thu Sep 13, 2007 3:24 pm

Posts
38

Favourite OS
Mac OS X 10.7
boxmaker wrote:
Thanks Unknown. I've just confirmed this using build 2296 and a virtual PC with 32 MB RAM. Back in 2001 it still worked with XP final, so I'm quite sure that build 2419 will also install.

Updated instructions:

1. open TXTSETUP.SIF with a text editor (it is just a huge text file)
2. search for "RequiredMemory"
3. change this entry to fit your needs.
4. save the file
5. open DOSNET.INF and do the same with "MinimumMemory"

Still I would recommend in-ISO hex editing to keep a bootable CD...

Do you guarantee this will work? When you tested it, did the first way not work and the second did? Because I'm wasting CD-R's like there ain't no tomorrow, and it was my dad that bought them. Oh well, he really doesn't need them because he never uses my computer, and he usually uses newer computers that can handle CD-RW's.
Thanks, I will try this.
And, nah, I won't do the in-ISO thing. I don't need to (and besides, the computer I'm editing these things with says it doesn't have enough memory to edit the ISO, even though it has 256 MB of RAM). My computer can't boot from CD's (although there's an option in the BIOS to do this, but it never worked for me) so it doesn't matter if I have a bootable CD or not.
Are you saying that it checks BOTH of those files to enforce the RAM requirement?
I also changed a value that appeared to be a HDD requirement, as I needed to override that one too.
Also, dosnet.inf also sounds like some sort of networking (for DOS) file. Is it really even used during Windows Setup?


Top  Profile  WWW
 PostPost subject:        Posted: Thu Sep 13, 2007 4:09 pm 
Reply with quote
Quote:
Do you guarantee this will work? When you tested it, did the first way not work and the second did?


I don't guarantee anything :wink:
In my first post, I was at work and posted what I remembered that I did a few years ago. Sorry that it didn't work for you.

My updated instructions (thanks to the unknown helper) were tested by creating a virtual PC in VMware with 32 MB RAM, booting from the (virtual) CD. With unmodified files, setup would stop complaining about 64 MB. With edited files, setup would continue to the next step (where I cancelled it).

DOSNET.INF is used. If it wasn't used, my first instructions would have worked.

But I guess you will not be happy with Whistler once you got it installed. Overriding HDD requirements is not the best one can do. Maybe there is not even enough space for setup to complete. And if it installs, it will run terribly slow (not because it is whistler, but because of RAM).


Top
 PostPost subject:        Posted: Thu Sep 13, 2007 11:25 pm 
Reply with quote
boxmaker wrote:
Thanks Unknown. I've just confirmed this using build 2296 and a virtual PC with 32 MB RAM.

NP. :wink:


jrdaigle1000 wrote:
Also, dosnet.inf also sounds like some sort of networking (for DOS) file. Is it really even used during Windows Setup?
A little googling goes a long way when you're unsure of what a file does. :wink:

Code:
PROCESS OVERVIEW
 ?    Modify the appropriate INF and SIF files.
 ?    Copy the vendor supplied drivers to the I386 share point.
 ?    Test the process.


IMPORTANT FILES

Filename          Location      Description

DOSNET.INF       I386          Defines which files to expand and copy
                                          to the workstation?s local drive during
                                         the first phase of the unattended setup. 
             These files are copied to the temporary directory structure.

TXTSETUP.SIF     I386         Defines which files to copy and where to
              copy them to during the second phase of theunattended setup. 
             These files are copied to their permanent directory structure.

Source
I also have it from experience that the dosnet.inf has system configuration minimum requirements
listed within as it's one of the 1st files to take action once the boot files have all loaded, & if booting from the CD or iso itself, then it determines what files are considered as bootup files.
If you check the contents of the file you'll see the list of what files are used as bootdisk/CD bootup files
Code:
[FloppyFiles.0]
d1,disk1,disk101
d1,ntdetect.com
d1,ntkrnlmp.exe
d1,setupldr.bin
d1,txtsetup.sif
d1,biosinfo.inf

[FloppyFiles.1]
d1,disk1,disk102
d1,hal.dll
d1,halacpi.dll
d1,halapic.dll
d1,halaacpi.dll
d1,drvmain.sdb
d1,setupreg.hiv
etc,etc,

[FloppyFiles.2]
d1,disk1,disk103
d1,cpqarray.sys
d1,atapi.sys
etc,etc,


[FloppyFiles.3]
d1,disk1,disk104
d1,ntdll.dll,system32\ntdll.dll
etc,etc,


Top
 PostPost subject:        Posted: Fri Sep 14, 2007 5:59 pm 
Reply with quote
FTP Access
Offline

Joined
Thu Sep 13, 2007 3:24 pm

Posts
38

Favourite OS
Mac OS X 10.7
Unknown wrote:
boxmaker wrote:
Thanks Unknown. I've just confirmed this using build 2296 and a virtual PC with 32 MB RAM.

NP. :wink:


jrdaigle1000 wrote:
Also, dosnet.inf also sounds like some sort of networking (for DOS) file. Is it really even used during Windows Setup?
A little googling goes a long way when you're unsure of what a file does. :wink:

Code:
PROCESS OVERVIEW
 ?    Modify the appropriate INF and SIF files.
 ?    Copy the vendor supplied drivers to the I386 share point.
 ?    Test the process.


IMPORTANT FILES

Filename          Location      Description

DOSNET.INF       I386          Defines which files to expand and copy
                                          to the workstation?s local drive during
                                         the first phase of the unattended setup. 
             These files are copied to the temporary directory structure.

TXTSETUP.SIF     I386         Defines which files to copy and where to
              copy them to during the second phase of theunattended setup. 
             These files are copied to their permanent directory structure.

Source
I also have it from experience that the dosnet.inf has system configuration minimum requirements
listed within as it's one of the 1st files to take action once the boot files have all loaded, & if booting from the CD or iso itself, then it determines what files are considered as bootup files.
If you check the contents of the file you'll see the list of what files are used as bootdisk/CD bootup files
Code:
[FloppyFiles.0]
d1,disk1,disk101
d1,ntdetect.com
d1,ntkrnlmp.exe
d1,setupldr.bin
d1,txtsetup.sif
d1,biosinfo.inf

[FloppyFiles.1]
d1,disk1,disk102
d1,hal.dll
d1,halacpi.dll
d1,halapic.dll
d1,halaacpi.dll
d1,drvmain.sdb
d1,setupreg.hiv
etc,etc,

[FloppyFiles.2]
d1,disk1,disk103
d1,cpqarray.sys
d1,atapi.sys
etc,etc,


[FloppyFiles.3]
d1,disk1,disk104
d1,ntdll.dll,system32\ntdll.dll
etc,etc,

Thanks for telling me how to do this! Whistler's installing right now! Does this same process work on XP? Vista?


Top  Profile  WWW
 PostPost subject:        Posted: Sat Sep 15, 2007 3:57 am 
Reply with quote
jrdaigle1000 wrote:
Thanks for telling me how to do this! Whistler's installing right now! Does this same process work on XP? Vista?

I'm sure it does, although the MinimumRam is sometimes listed as
RequiredRam in some of the builds inf files.


Top
 PostPost subject:        Posted: Thu Sep 20, 2007 9:31 pm 
Reply with quote
FTP Access
Offline

Joined
Thu Sep 13, 2007 3:24 pm

Posts
38

Favourite OS
Mac OS X 10.7
How do I remove the system requirements from Windows Longhorn Build 4008. First thing it does is tell me it requires 128 MB of RAM. The beforementioned files were edited by me. They stated the requirement as 64 MB. What are ALL the files in Longhorn that contain requirements I need to change?


Top  Profile  WWW
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 17 posts ] 




Who is online

Users browsing this forum: No registered users and 14 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
Jump to:  

All views expressed in these forums are those of the author and do not necessarily represent the views of the BetaArchive site owner.

Powered by phpBB® Forum Software © phpBB Group

Copyright © 2006-2018

 

Sitemap | XML | RSS