FBA error

  • Thread starter Thread starter Fenster
  • Start date Start date
F

Fenster

I'm new to XPe so please bear with me if I've missed something obvious.

I created a basic XPe image about two weeks ago that I copied to a
clean/empty/recently formatted partition and successfully booted from
(first boot, multiple reboots on different days, etc.).

Times have moved on but I wanted to go back to that raw (i.e. pre-FBA)
image but when I copy it to the partition (after formatting it first) I
get an error from FBA.EXE: "The instruction at 0x03592F5D referenced
memory at 0x0000000C. The memory could not be written."

Other things that may be relevant (in no particular order):

1. The error occurs when FBA is about two thirds through installing
devices.

2. I'm using the evaluation version of the XPe tools.

3. The whole PC was rebuild from scratch about a month ago (so
presumably the 90-120 day licence isn't the problem).

4. I'm not aware of anything that's been changed on the PC in the
intervening weeks (other than different XPe targets being successfully
booted on the same partition, none of which work now).

5. The PC is dual-boot and the regular desktop XP stills works fine.

6. The mouse/keyboard (both USB) don't seem to function during FBA at
all. I base this on not being able to toggle Caps Lock or Num Lock or
being able to move the mouse cursor around the screen. Maybe this
expected but when the error message is displayed there's a very tempting
OK button that I can't press. :(

Thanks for any help.
 
Fenster said:
I'm new to XPe so please bear with me if I've missed something
obvious.
I created a basic XPe image about two weeks ago that I copied to a
clean/empty/recently formatted partition and successfully booted from
(first boot, multiple reboots on different days, etc.).

Times have moved on but I wanted to go back to that raw (i.e. pre-FBA)
image but when I copy it to the partition (after formatting it first)
I get an error from FBA.EXE: "The instruction at 0x03592F5D referenced
memory at 0x0000000C. The memory could not be written."
Click to expand...

Have you changed your image at all since you created the last one that
worked? This sounds suspiciously like having wrong drive letters in your
configuration's settings.
 
Fenster,

Also, can you look at the FBA log and see where it left off? It's in
...\Windows\FBA\fbalog.txt.

HTH,
Brad
 
"Gordon Smith said:
Have you changed your image at all since you created the last one that
worked? This sounds suspiciously like having wrong drive letters in your
configuration's settings.
Click to expand...
I haven't changed the image at all (not consciously anyway) and I don't
think I've changed the hardware since it was last used. The exception
being the mouse and keyboard which may be in different USB sockets
because I have to swap them around a bit when booting the PC into "DOS"
mode but that's another story.

However, I did go trawling through the image after I posted yesterday
and I found the FBA log. Sure enough, the drive letter/directory was
invalid, it seemed to pointing at C: rather than E: which leads me to
another question.

When I'm developing the target image (from a system based on C:) I have
a dual boot to C: and E: but on E: there's the single boot system (the
target image). Does this mean that I have to develop for E: but
recompile for C: when the target image is being readied for deployment
(on a system only has a C: drive)?
 
Fenster said:
When I'm developing the target image (from a system based on C:) I
have a dual boot to C: and E: but on E: there's the single boot
system (the target image). Does this mean that I have to develop for
E: but recompile for C: when the target image is being readied for
deployment (on a system only has a C: drive)?
Click to expand...

Yes. Most people don't develop on the same hardware, but if you do one
thing you can do to make life easier is to have C: always be your XPE image
and put XP Pro (for development) on your 2nd partition instead of the other
way around.
 
Back
Top