CommieChipmunk
Member
+488|7041|Portland, OR, USA

Bertster7 wrote:

CommieChipmunk wrote:

=[AUT]-[phoenix]= wrote:


just wait till the first service pack is out....at the moment most of the drivers suck....
most? heh. try all of the drivers suck.

I can't play bf2 anymore, it's a fucking slideshow.
I don't currently have it installed, but I was running Ultimate 64-bit for a while, I had decent drivers for everything - you must just be unlucky.
BF2 ran perfectly, as did every other game I tried - which wasn't many.

It's the software incompatibilities that pissed me off.
I know, it used to work.. now it just doesn't it's weird...

most every other game looks fine though.
CommieChipmunk
Member
+488|7041|Portland, OR, USA
...damn

Okay so I installed XP on the second partition, but when it says:

Boot from disk:


...press any key to continue - right underneath that it says

"disk read error has occured, press ctrl + alt + delete to restart

How do I boot into xp?
Scorpion0x17
can detect anyone's visible post count...
+691|7237|Cambridge (UK)

Bertster7 wrote:

Scorpion0x17 wrote:

Bertster7 wrote:

That's just not true.

The CPU must be able to identify each individual memory location, to do this each location must have a unique address. The fact that the OS and the BIOS have access to the full 4GB of physical RAM is completely irrelevant, since the CPU can't see it - only the available logical addresses, which includes the IO addressing (since the CPU needs to be able to access IO devices and memory). Therefore the total amount of memory available is 4GB of logical memory. Any virtual memory is simply handled through a page management system - with no pages exceeding the maximum addressable size by the CPU. The OS can't do anything without the CPU, so if the CPU can't see it - it isn't there.

You can put 4GB of physical RAM in a 32-bit system, it just won't all be used. Some of the physical RAM will be unavailable.
Will you please haul your ass into the 21st century!

Intel wrote:

2.1.3 The Intel386™ Processor (1985)
The Intel386 processor was the first 32-bit processor in the IA-32 architecture family.
It introduced 32-bit registers for use both to hold operands and for addressing. The
lower half of each 32-bit Intel386 register retains the properties of the 16-bit registers
of earlier generations, permitting backward compatibility. The processor also
provides a virtual-8086 mode that allows for even greater efficiency when executing
programs created for 8086/8088 processors.
In addition, the Intel386 processor has support for:
• A 32-bit address bus that supports up to 4-GBytes of physical memory
• A segmented-memory model and a flat memory model
• Paging, with a fixed 4-KByte page size providing a method for virtual memory
management
• Support for parallel stages

(Source(page 34))
Intel386! 1985! "A 32-bit address bus"! "supports up to 4-GBytes of physical memory"!

I rest my case.
Well that's pretty damned obvious. The CPU provides an offset which the paging unit uses to generate the address in physial memory - BUT the thing that makes me (and a lot of other people) refer to it as logical memory, is that some of that space in physical memory (after address allocation by the paging unit) is taken up by IO devices controlled by the BIOS. The BIOS reserves space in memory for PCI/AGP etc. - after address translation by the paging unit this space is the reason the OS won't report 4GB of memory present. This is why I'm refering to it as logical memory - because it includes IO address space, hence it is logical memory.

I know technically you CAN support more memory than that within 32-bit systems (using PAE and AWE and stuff - but it's a bit slow), but I don't think Vista does that - why bother when there's a 64-bit version?
Please re-read what I posted - I specifically used the term physical memory for exactly that reason - physical memory is physical memory no matter what it's used for.

You are correct in saying that the OS and apps will not have access to the full amount, but that is not the same saying that a 32bit system (whether it's running Vista, XP, or any older 32bit version of windows (and also irrespective of the processor (as long as it is a 32bit processor)) does not support 4GB of physical RAM.

Which is what I stated in the first place.

(oh and your claim that the CPU can't see the whole 4GB, because the BIOS allocates some for IO addressing, is also wrong. The BIOS can do nothing without the CPU - the BIOS is just machine code that runs on the CPU, it's not a seperate processor - therefore it is actually the CPU that does the IO memory reservation and it is the CPU that sees the full 4GB)

Last edited by Scorpion0x17 (2007-06-28 19:09:43)

CommieChipmunk
Member
+488|7041|Portland, OR, USA

CommieChipmunk wrote:

...damn

Okay so I installed XP on the second partition, but when it says:

Boot from disk:


...press any key to continue - right underneath that it says

"disk read error has occured, press ctrl + alt + delete to restart

How do I boot into xp?
Scorpion0x17
can detect anyone's visible post count...
+691|7237|Cambridge (UK)

CommieChipmunk wrote:

...damn

Okay so I installed XP on the second partition, but when it says:

Boot from disk:


...press any key to continue - right underneath that it says

"disk read error has occured, press ctrl + alt + delete to restart

How do I boot into xp?
Erm... that sounds bad...

Test your drive with Hitachi Drive Fitness Test (don't worry if your HDD is not a Hitachi - it should still work OK (as far as I am aware (I have successfully used it to test non-Hitachi drives (but I can't guarantee that it'll definately work on all drives (but can see no reason why it shouldn't)))).
CommieChipmunk
Member
+488|7041|Portland, OR, USA

Scorpion0x17 wrote:

CommieChipmunk wrote:

...damn

Okay so I installed XP on the second partition, but when it says:

Boot from disk:


...press any key to continue - right underneath that it says

"disk read error has occured, press ctrl + alt + delete to restart

How do I boot into xp?
Erm... that sounds bad...

Test your drive with Hitachi Drive Fitness Test (don't worry if your HDD is not a Hitachi - it should still work OK (as far as I am aware (I have successfully used it to test non-Hitachi drives (but I can't guarantee that it'll definately work on all drives (but can see no reason why it shouldn't)))).
it ended up being okay I can boot now... but I just don't know how to boot into the second partition.
Scorpion0x17
can detect anyone's visible post count...
+691|7237|Cambridge (UK)

CommieChipmunk wrote:

Scorpion0x17 wrote:

CommieChipmunk wrote:

...damn

Okay so I installed XP on the second partition, but when it says:

Boot from disk:


...press any key to continue - right underneath that it says

"disk read error has occured, press ctrl + alt + delete to restart

How do I boot into xp?
Erm... that sounds bad...

Test your drive with Hitachi Drive Fitness Test (don't worry if your HDD is not a Hitachi - it should still work OK (as far as I am aware (I have successfully used it to test non-Hitachi drives (but I can't guarantee that it'll definately work on all drives (but can see no reason why it shouldn't)))).
it ended up being okay I can boot now... but I just don't know how to boot into the second partition.
Hmm... do you not get a menu appear now during boot up (just after the POST, but before windows kicks in)?
Bertster7
Confused Pothead
+1,101|7053|SE London

Scorpion0x17 wrote:

Bertster7 wrote:

Scorpion0x17 wrote:

Bertster7 wrote:

That's just not true.

The CPU must be able to identify each individual memory location, to do this each location must have a unique address. The fact that the OS and the BIOS have access to the full 4GB of physical RAM is completely irrelevant, since the CPU can't see it - only the available logical addresses, which includes the IO addressing (since the CPU needs to be able to access IO devices and memory). Therefore the total amount of memory available is 4GB of logical memory. Any virtual memory is simply handled through a page management system - with no pages exceeding the maximum addressable size by the CPU. The OS can't do anything without the CPU, so if the CPU can't see it - it isn't there.

You can put 4GB of physical RAM in a 32-bit system, it just won't all be used. Some of the physical RAM will be unavailable.
Will you please haul your ass into the 21st century!


Intel386! 1985! "A 32-bit address bus"! "supports up to 4-GBytes of physical memory"!

I rest my case.
Well that's pretty damned obvious. The CPU provides an offset which the paging unit uses to generate the address in physial memory - BUT the thing that makes me (and a lot of other people) refer to it as logical memory, is that some of that space in physical memory (after address allocation by the paging unit) is taken up by IO devices controlled by the BIOS. The BIOS reserves space in memory for PCI/AGP etc. - after address translation by the paging unit this space is the reason the OS won't report 4GB of memory present. This is why I'm refering to it as logical memory - because it includes IO address space, hence it is logical memory.

I know technically you CAN support more memory than that within 32-bit systems (using PAE and AWE and stuff - but it's a bit slow), but I don't think Vista does that - why bother when there's a 64-bit version?
Please re-read what I posted - I specifically used the term physical memory for exactly that reason - physical memory is physical memory no matter what it's used for.

You are correct in saying that the OS and apps will not have access to the full amount, but that is not the same saying that a 32bit system (whether it's running Vista, XP, or any older 32bit version of windows (and also irrespective of the processor (as long as it is a 32bit processor)) does not support 4GB of physical RAM.

Which is what I stated in the first place.

(oh and your claim that the CPU can't see the whole 4GB, because the BIOS allocates some for IO addressing, is also wrong. The BIOS can do nothing without the CPU - the BIOS is just machine code that runs on the CPU, it's not a seperate processor - therefore it is actually the CPU that does the IO memory reservation and it is the CPU that sees the full 4GB)
I mention the IO reservation being done by the BIOS because the configuration set in the BIOS (editing a load of machine code, like you say) determines how much IO address space is used, turning things off will increase the RAM available, therefore it is, as I said, controlled by the BIOS. Nothing to do with it being a seperate processor, it is the instructions that control it - not any action taken.

If 4GB of memory is not present in a system the IO addressing will not take up any of the available physical memory, so you don't lose anything. If you are at the 4GB limit, you start eating into your memory with IO. The memory isn't being used for IO, just the address apace - making some of the physical RAM inaccessible.

Hmmm.....      Some address space being used for purposes other than addressing physical memory, combined with address space for accessing physical memory - sounds an awful lot like logical memory to me - practically a textbook definition.

If the physical memory is all so supported and accessible, why isn't it addressable through the OS? Why can't some of the physical memory be used? Oh, that's right, some of the addresses are asigned to IO. Therefore 4GB of physical memory is not properly supported

You're just being fooled by Intel's marketing ploys, using the most favourable sounding language. It can address 4GB of physical memory, it just doesn't.

Scorpion0x17 wrote:

You are correct in saying that the OS and apps will not have access to the full amount, but that is not the same saying that a 32bit system (whether it's running Vista, XP, or any older 32bit version of windows (and also irrespective of the processor (as long as it is a 32bit processor)) does not support 4GB of physical RAM
Ummmm.....

Yes it is. Like I said earlier, you can put 4GB in, you just can't use it all. That's not being properly supported.

Any other component within a computer system that did not provide full functionality in a particular environment cannot be claimed to be properly supported. Nor can 4GB of memory.


What is supported is 4GB of logical memory. IO space + available physical memory space.
Zimmer
Un Moderador
+1,688|7227|Scotland

We should actually make a new topic, put the best arguments for and against this topic and see the conclusion. You guys are doing a great job at keeping me entertained.
Bertster7
Confused Pothead
+1,101|7053|SE London

CommieChipmunk wrote:

...damn

Okay so I installed XP on the second partition, but when it says:

Boot from disk:


...press any key to continue - right underneath that it says

"disk read error has occured, press ctrl + alt + delete to restart

How do I boot into xp?
You're booting into Vista right?
Don't worry about the disk read error, just sounds like you had your boot sequence wrong or something.

I hope you are booting into Vista, since the Vista OS selection screen takes preceedence over the older windows boot.ini. There is no longer a boot.ini file within Vista, so you need to use the Bcdedit.exe commandline app to configure your boot options.

When you reboot you should see the boot options screen, with the option to boot; Vista, an Earlier Version of Windows or run a memory test. To boot XP, select the earlier windows version.
CommieChipmunk
Member
+488|7041|Portland, OR, USA

Bertster7 wrote:

CommieChipmunk wrote:

...damn

Okay so I installed XP on the second partition, but when it says:

Boot from disk:


...press any key to continue - right underneath that it says

"disk read error has occured, press ctrl + alt + delete to restart

How do I boot into xp?
You're booting into Vista right?
Don't worry about the disk read error, just sounds like you had your boot sequence wrong or something.

I hope you are booting into Vista, since the Vista OS selection screen takes preceedence over the older windows boot.ini. There is no longer a boot.ini file within Vista, so you need to use the Bcdedit.exe commandline app to configure your boot options.

When you reboot you should see the boot options screen, with the option to boot; Vista, an Earlier Version of Windows or run a memory test. To boot XP, select the earlier windows version.
hmm.  I typed bdcedit.exe into run? was that what I was supposed to do?  Is there any way that I can get a screen to pop up so that I can decide which OS I want to boot with?
Bertster7
Confused Pothead
+1,101|7053|SE London

CommieChipmunk wrote:

Bertster7 wrote:

CommieChipmunk wrote:

...damn

Okay so I installed XP on the second partition, but when it says:

Boot from disk:


...press any key to continue - right underneath that it says

"disk read error has occured, press ctrl + alt + delete to restart

How do I boot into xp?
You're booting into Vista right?
Don't worry about the disk read error, just sounds like you had your boot sequence wrong or something.

I hope you are booting into Vista, since the Vista OS selection screen takes preceedence over the older windows boot.ini. There is no longer a boot.ini file within Vista, so you need to use the Bcdedit.exe commandline app to configure your boot options.

When you reboot you should see the boot options screen, with the option to boot; Vista, an Earlier Version of Windows or run a memory test. To boot XP, select the earlier windows version.
hmm.  I typed bdcedit.exe into run? was that what I was supposed to do?  Is there any way that I can get a screen to pop up so that I can decide which OS I want to boot with?
No, not exactly.

Yes, you can get a screen up with boot options, that's what Bcdedit.exe is for. You don't type it in the run box, you run it from a command line.

Here are some instructions - it gets a bit complicated compared to old school boot.ini editing.

http://www.microsoft.com/whdc/driver/ti … vista.mspx

That tells you everything you need to know.

Bootcfg.exe could probably be used to achieve similar results - but I've never used it.

Last edited by Bertster7 (2007-06-29 16:04:32)

CommieChipmunk
Member
+488|7041|Portland, OR, USA
Bertster7
Confused Pothead
+1,101|7053|SE London

CommieChipmunk wrote:



wtf is going on?!
That's quite comprehensive instructions.

It's not very hard.
CommieChipmunk
Member
+488|7041|Portland, OR, USA

Bertster7 wrote:

CommieChipmunk wrote:



wtf is going on?!
That's quite comprehensive instructions.

It's not very hard.
I know, i just did it but it doesn't work...

my boot options are:

Debug entry
Windows Vista


when I boot with the debug entry it doesn't really do anything..  why doesn't it recognize XP?

Last edited by CommieChipmunk (2007-06-29 17:49:15)

Board footer

Privacy Policy - © 2025 Jeff Minard