Problem with pagefile during FBA

[Ricky]

I have a problem starting my configuration of XPe.
The FBA, during the "Processing runonce items" phase tells me that the
system is low on virtual memory. After that the FBA phase proceeds but when
I start the system the paging file is set to 0 (and, if I try to set it
manually through the system properties interface and reboot it remains to
0) and some components doesn't work.

My system has 128 MB RAM, I setted up paging files through "Standard PC"
components to 256-256 or 128-256 with no luck, I use a 1 GB CF card
(formatted to NTFS) without EWF as boot HD.

Anyone can help me, please?

Thanks a lot.

Ricky

 

[KM]

Ricky,

Well, I suppose it is not an issue to set up pagefile before FBA (you will just have to manually set up corresponding registry
entries if TD doesn't do a good job there).
However, the real problem is that you can't enable the pagefile at run time, after FBA. Did I get this right?

A few things to check:

- Any chance your boot device (CF) is removable? Should be marked as fixed.

- Do you have enough space on the boot partition to create the pagefile? (please note: *boot* partition is the one where you
have ntldr on)

- Is the pagefile.sys getting actually created? (even if it is 0-sized)
What is the storage configuration (partitions) on your target?

- If you manually set the "PagingFiles" value of the [HKML\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management]
key, does it create pagefile on the next boot?

- Is "Primitive: Dbghelp" component in your Configuration?

- Do you have "Disk Dump Drivers" component included in the image config? (not directly related but may better have it in)

 

[Ricky]

- Any chance your boot device (CF) is removable? Should be marked as fixed.

My CF, a sandisk Ultra II 1GB, is removable.
Is there any way to solve it?

Thanks a lot.

 

[KM]

Ricky,

Well, you will have to mark it as fixed.
Typically it is done using manufacturer provided tools.
Some manufactuers sell already fixed cards, some don't. I'd try contacting
Sandisk to get the utility that applies specifically to your CF type. A few
relevant Sandisk contacts have been posted in this NG, you may try to use
them if you don't have a good one.

Regards,
KM

 

[Sean Liming \(eMVP\)]

SanDisk use to have a utility, but they don't give it out anymore. In fact
some folks on the newsgroup, mentioned that SanDisk is no longer offering
fixed versions any more. With the merger with M-Systems who know if they
will change direction again.

Other manufaturers off fixed CF cards: WinSystems, Simpletech -
http://www.seanliming.com/flashhelp.html

If you use the new EWF RAM-REG setting or FBWF - you will not have to worry
about a second partition, thus removeable CF would work jsut as well.

Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
XP Embedded Book Author - XP Embedded Advanced, XP Embedded Supplemental
Toolkit

 

[KM]

If you use the new EWF RAM-REG setting or FBWF - you will not have to worry about a second partition, thus removeable CF would

work jsut as well.

But not the pagefile :-(

 

[Ricky]

If you use the new EWF RAM-REG setting or FBWF - you will not have to worry
about a second partition, thus removeable CF would work jsut as well.

But my probs are related to pagefile.
I don't think that my image, with web server, smtp, rdp, will work with 128
MB without pagefile. Am I right?

Ricky

 

[KM]

Ricky,

RDP client or server?

If your web server was Appache and you only used RDP client (connecting to other devices), I'd say you may still be good with 128M
RAM. Especially if you go with Minlogon based image.

Btw, it is a bit scary to use CF (removable or not) without EWF or FBWF protection. Since you are probably going to end up using RAM
overlay protection, you'd need more RAM if your apps do lots of disk writes.

With the pagefile on you are going to wear out your CF very quickly.