|
When I run the setup on Windows Server 2003 (for SBS edition) it tells me it isn't supported because it is less than SQL Server 2000 SP2. I've installed it before so I knew it was coming. Previously I have just ignored that message, and installed the SP straight afterwards.
Even the official workaround states this: http://support.microsoft.com/default.aspx?scid=kb;en-us;329329[^]
Yet this time when the setup loads, before the wizard shows I get this message:
---------------------------
Setup
---------------------------
Microsoft SQL Server 2000 Developer Edition server component is not supported on this operating system. Only client components will be available for installation.
---------------------------
OK
---------------------------
So how do I install the server in order to apply the SP3? Only the client tools option is enabled in the setup. 
|
|
|
|
|
David Wulff wrote:
So how do I install the server in order to apply the SP3?
Find the CD Office XP professional edition. And try to find the folder MSDE2000. Then run the setup file. Then you will be able to confige the database as database server.
A thousand mile of journey, begin with the first step.
APO-CEDC
Save Children Norway-Cambodia Office
|
|
|
|
|
Can you explain a bit more to me, please? Where do I find the Office XP professional edition CD. Is that MSDE? I have a DVD MSDN Universal subscription + licenses for SBS, SQL Server 2000 and Office.
And surely this isn't the way you are meant to install SQL Server 2000 on a Windows Server 2003 machine? They are both current top-line serve systems sold by Microsoft so they must be compatible. Is my SBS installation maybe messed up to disable to the SQL Server installation?
|
|
|
|
|
I've only done this install about 30 times using an MSDN Subscription to SQL Server. I have never seen this problem before. I would suggest a few things.
If you burned from an ISO burn again using a slower burn speed. If you are installing from a DVD, copy out the SQL Server install folder and burn it in the root structure of a CD. The installer was never meant to run from a DVD run it from a CD (that may sound weird but it has never failed me ever).
If that does not work copy the contents into a folder on the server and run the installation from there.
Lastly, make sure you are logged on as "Administrator".
- Rex
My name is Maximus Decimus Meridius, commander of the Armies of the North, General of the Felix Legions, loyal servant to the true emperor, Marcus Aurelius. Father to a murdered son, husband to a murdered wife. And I will update my website, in this life or the next.
Code-frog System Architects, Inc.
|
|
|
|
|
code-frog wrote:
If you burned from an ISO burn again using a slower burn speed. If you are installing from a DVD, copy out the SQL Server install folder and burn it in the root structure of a CD. The installer was never meant to run from a DVD run it from a CD (that may sound weird but it has never failed me ever).
I haven't used ISO images, I used the installs directly from the folder on the DVD. I will try burning it on a CD and running it from there as you say.
code-frog wrote:
If that does not work copy the contents into a folder on the server and run the installation from there.
If the CD fails, I'll try that too.
code-frog wrote:
make sure you are logged on as "Administrator".
I am.
|
|
|
|
|
Hi,
I've created Disk filter driver based on diskperf and I need to Create/Read/Write my c:\\myFile.dat. But I can't nor create nor read and write the file. I tried these operations from everywhere  , also I created a system thread but the result is same.
I'm using ZwXXX functions. The only place from where I can open and read the file is IoControl, but the status code for ZwWriteFile is STATUS_NOT_IMPLEMENTED.
Please, tell me how workaround this problem ?
many thanks and sorry for weak english.
|
|
|
|
|
I have a device with Bluetooth which I am trying to communicate with. I am using the Windows XP drivers on my PC.
I can pair with the device and use it without problems, until it is switched off or goes out of range. Then I have to 'Remove' it from the list of Paired devices & pair again.
I don't think this is right because Microsoft say if its on the list it should still be paired. Anyone else got any experience of this?
Ali
|
|
|
|
|
I am trying for network printing by firing job from Mac OS acting as a client and Windows XP OS as a server.
I see that spool file is not getting created properly on windows xp when
windows default LPD server is running, but when we ignore the Data Length of spool file in LPD service by writing new LPD service at windows end, then it works fine and now spool file is got created on windows server, when we fire print jobs from Mac OS.
This is because Mac sends by default 1 TeraByte of data to Windows OS,
which we have to ignore at windows end otherwise we cannot get the spool
file created at windows end.
But this change in implementing LPD service by ignoring Data length can
effect or have impact when we fire jobs from other OS like Windows 2k, Win
98, Win ME, etc as a client. Since only one LPD service can be in running
mode or is eligible to run within the Operating System.
Therefore my question was that what will be the effect on other OS printing
as a client to Windows XP, if we change the implementation of default LPD
service by ignoring the Data length of the spool file in order to support
Mac OS printing as a client ?
|
|
|
|
|
I have been working on a real time project which is highly dependent on the system clock of PC.
But my team members are very much worried of the "Drift in the System Clock"?
Can any body give some hint what it is and what are the solutions to come over this problem.
Thanks in Advance
Anil Kumar
|
|
|
|
|
'Drift' is basically when the system clock deviates from the actual wall clock time. It can occur when the actual system clock interrupt period is different from that programmed in, or when handling of the clock interrupt is delayed, although this is unlikely since the clock interrupt has a high priority. The first can occur either through systemic errors such as a badly tuned clock circuit which always 'ticks' faster or slower than programmed, or simply through variation in the tick rate due to changes in the values of components with temperature. PC real-time clock circuits typically aren't very accurate.
Windows NT-based operating systems support modifying the real-time clock adjustment - the amount added to the real-time clock at each clock interrupt. This feature is generally used to slowly correct a large error. This only affects the system clock, not the value returned by GetTickCount. The clock resolution can be varied by system; ClockRes[^] says mine is currently 15.625ms.
Stability. What an interesting concept. -- Chris Maunder
|
|
|
|
|
Hi Mike,
Thanks first for the reply, As you have mentioned that Drift in the system clock is due to not Handling the clock interrupt properly(Not exactly at the programmed time sooner or later). If this is the case then in embedded systems like (Mobile phones and PDAs) where applications are very time critical then it is the responsibility of the RTOS to provide the best Clock or GetTickCOunt functionality.
Specialy in my project where i am Handling the Audio/Video Synchronization i can ask my RTOS provider for this or if there is a way to know that drift at software level and compensate it.
Any comment will be very useful.
Regards
Anil Kumar
|
|
|
|
|
Hi
I know that the answer is related to HIGH-RESOLUTION-TIMER which sets windows timer exactly in correct 1 millisecond intervals.
I don't know how to use or set it, you can search the internet. but I know that all mediaplayers, use this for audio/video sync.
So search the internet for High Resolution Timer.
hope it helps
|
|
|
|
|
I've recently upgraded the RAM on my PC and now windows fails to start. I installed a new version of windows in a secondary HD partition and that works fine, but I'd rather keep my existing installation.
Regardless of how I try and start it, it will always fail. It either reboots before getting to a login prompt, or I get a BSOD - Even in Safe Mode, VGA Mode, or Command Prompt mode.
The only thing that I can see differently between the two installations (the previous and the emergency one I created) is that the new emergency install has only default drivers.
The BSOD messages are various things - but one constant is that at the point that it switches to the Hi-res video it fails.
Any ideas?
Any ideas of how to change the video driver when I can't get it to boot at all?
My: Blog | Photos
WDevs.com - Open Source Code Hosting, Blogs, FTP, Mail and More
|
|
|
|
|
In my opinion, your computer might have a problem with conflict with the IRQ or any hardware resource with an old system. Try to access your computer with an SAFE MODE and check your computer hardware resources. If it is possible, try to make change to it. If you still could not boot to windows at all, try to use Bart PE[^] in order to access your computer from the CDROM.
A thousand mile of journey, begin with the first step.
APO-CEDC
Save Children Norway-Cambodia Office
|
|
|
|
|
The man from SCN-CO wrote:
Try to access your computer with an SAFE MODE and check your computer hardware resources
As I mentioned regardless of how I try and start it, it will always fail. It either reboots before getting to a login prompt, or I get a BSOD - Even in Safe Mode, VGA Mode, or Command Prompt mode.
The man from SCN-CO wrote:
If you still could not boot to windows at all, try to use Bart PE in order to access your computer from the CDROM.
I'm able to access the PC by installing windows on a secondard disk partition, so I am unsure what BartPE will give me over that. Can I use it to change the drivers in my original windows installation. I couldn't see how on the web page.
My: Blog | Photos
WDevs.com - Open Source Code Hosting, Blogs, FTP, Mail and More
|
|
|
|
|
When you say upgraded - do you mean new (faster) memory, or just more of it? I assume you've tried the obvious of putting the memory back as it was - what happens if you do that?
|
|
|
|
|
|
My two suggestions would be:
1) Put in another video card (if you have one)
2) Install Windows again "over the top" of the first partition. That *should* give you generic video drivers again, without any data loss.
|
|
|
|
|
What version of windows?
I almost agree with the try a different video card but that should not be different than starting in safemode. So I would ask what other cards do you have installed and taking any extra out may let the machine start up.
The times I have seen your description have followed moving the hard drive to a new machine and not having the correct IDE drivers or putting in more than 512 on a Win ME box (ASUS MB in that case).
I do not mind getting old. It beats all the other options that I can think of.
|
|
|
|
|
Michael A. Barnhart wrote:
What version of windows?
Windows XP SP 2 - All patched up-to-date.
Michael A. Barnhart wrote:
So I would ask what other cards do you have installed and taking any extra out may let the machine start up.
No other cards. Just some USB devices: Memory card reader, ADSL Modem and Printer.
My: Blog | Photos
WDevs.com - Open Source Code Hosting, Blogs, FTP, Mail and More
|
|
|
|
|
Again the only time I have seen that is when migrating the disk with out the new ide drivers.
You say you have put the old memory back in and the same responce. Do you have two sticks of memory. Just maybe swaping the order, even if they check ok. one was not quite in sink? This is a strech.
I think you were wise in just enjoying the chocolate. If you are ever in Kansas City (not sure MO or KS) but I hear they have a chocolate restraunt. even the chery on the sundays is chocolate filled. I have never been there however.
I do not mind getting old. It beats all the other options that I can think of.
|
|
|
|
|
|
Colin Angus Mackay wrote:
The BSOD messages are various things - but one constant is that at the point that it switches to the Hi-res video it fails.
I've actually had this happen, from the exact same upgrade. The new memory I had gave bad memory responses (read does not match write) which slowly corrupted windows. Even reinstallation resulted in corruption as soon as it reached the non-dos portion of the install.
Graphics and memory are shared to some extent. DirectX sets up virtual buffers, shifting graphics information through real-memory before going to the graphics card. The amount of memory on the graphics card determines how much is shifted down. Until Vista, windows itself uses very little graphics acceleration, it's mostly IO from real-memory.
My suggestion is pull out the new memory. Recreate your new partition (leave your original alone for now until you get the problem fixed). Run a memory test, it should come in good unless you got a static discharge on your original memory, which has only happened once at work.
If you have success, install the memory one at a time if your motherboard allows you to and repeat the tests. Until you get a successful installation and run of windows on the new partition, don't write over your old.
If, and only if, a full memory diagnostic shows the new memory is good, then do a repair on the original partition and it should come back to life.
_________________________
Asu no koto o ieba, tenjo de nezumi ga warau.
Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
|
|
|
|
|
|
First, You did backup before doing the upgrade? 
To test out the memory config, use memtest[^] once you make the CD you can test your system without booting into windows.
For your current problem.
1. like others have said go back to your old config. Then clear out the BIOS settings with the jumper on your motherboard. Also make sure you have the latest BIOS as well as double checking that your motherboard supports the configuration.
2. As far as fixing your windows install. If the error is not in the same place, there is a good chance it is memory or seating related. Make sure the video and all the cards are in well by pulling them out and putting them back in. Double check that the memory is seated correctly. If it is driver related, then safe mode should allow you to work around it. Also make sure you check the video card knowledge base for the specific problem before you do anything drastic.
3. If you've installed a sparate copy of windows on a different drive, then I'd move your data over to that installation rather then deal with an install over the top. I gave up trying that a long time ago because it always had a very low chance of success.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
