rob.mccombe
Hi every one i have just installed my virtual dj 5.2.1 on windows 7.
Just to let you know it worked fine no probs at all for a quick hour mix.
Not sure about the mappers and midi controllers but i have had no problems installing vista drivers for my hardware as windows 7 is basically vista but just not as memory hungry.
I am still testing and i will push it to the limits so will keep u guys updated.
Just to let you know it worked fine no probs at all for a quick hour mix.
Not sure about the mappers and midi controllers but i have had no problems installing vista drivers for my hardware as windows 7 is basically vista but just not as memory hungry.
I am still testing and i will push it to the limits so will keep u guys updated.
Posted Sun 01 Feb 09 @ 9:42 pm
metroplex2005
windows 7 is still beta. they can change a lot of things for the final release, if it works now, its fine but no proof for the future.
Posted Mon 02 Feb 09 @ 1:34 pm
rob.mccombe
They wont change much only the aero and style as windows 7 is built on the same basis as vista. I have tried 17 bits of different hardware on windows 7 and the vista drivers have worked with all 17 of them without a problem.
I can also confirm that the bcd3000, numark total control and the Rmx work on windows 7.
windows 7 might be beta at present but alot of people use these until they can get a illegal final release version.
Thats why i put this information on here for people who might be looking at giving windows 7 a try so that they know what works.
Me my self will be buying windows 7 as it is loads better
I can also confirm that the bcd3000, numark total control and the Rmx work on windows 7.
windows 7 might be beta at present but alot of people use these until they can get a illegal final release version.
Thats why i put this information on here for people who might be looking at giving windows 7 a try so that they know what works.
Me my self will be buying windows 7 as it is loads better
Posted Mon 02 Feb 09 @ 7:44 pm
djcrossfade1200
i cant wait to upgrade
Posted Mon 02 Feb 09 @ 11:22 pm
markdeejay75
Refering to Cstoll > XP, look in add / remove programs, the tabs on the left there is 'Set Program Access and Defaults'
This should let you select Firefox as the default browser.
There might also be an option within Firefox to make it the default browser.
This should let you select Firefox as the default browser.
There might also be an option within Firefox to make it the default browser.
Posted Tue 03 Feb 09 @ 11:51 am
cstoll
It's not an issue of setting it as the default browser ... I know how to do that ... but for example ...
On my XP desktop Firefox is the default browser, however; if I click on a link in Outlook Express it will open it in IE. And yes, there are probably settings that I can change in Outlook and elsewhere. But with Win7 - install FF and set as default -- presto DONE everything opens in FF regardless of application.
Also, just to elaborate more on the environment and what I am trying to say ...
When I got my MAC and started using OSX, I began to feel like the operating system was 'listening' to me and when I would make a setting it was adhered to. I have that same 'FEEL' with Win7, if I make a setting the operating system listens. I know its a bit blasphemous to compare OSX and windows in the same paragraph ... And maybe it is because I am running Win7 on my MacBook Pro is why it feels the same ...? LOL
On my XP desktop Firefox is the default browser, however; if I click on a link in Outlook Express it will open it in IE. And yes, there are probably settings that I can change in Outlook and elsewhere. But with Win7 - install FF and set as default -- presto DONE everything opens in FF regardless of application.
Also, just to elaborate more on the environment and what I am trying to say ...
When I got my MAC and started using OSX, I began to feel like the operating system was 'listening' to me and when I would make a setting it was adhered to. I have that same 'FEEL' with Win7, if I make a setting the operating system listens. I know its a bit blasphemous to compare OSX and windows in the same paragraph ... And maybe it is because I am running Win7 on my MacBook Pro is why it feels the same ...? LOL
Posted Tue 03 Feb 09 @ 12:12 pm
metroplex2005
rob.mccombe wrote :
They wont change much only the aero and style as windows 7 is built on the same basis as vista.
if you are a programmer from windows 7 i belive you.
if you are not, you just think that they wont change much.
and if you are not a programmer of windows 7, in fact you will know nothing about they will change or not.
because it is a beta version of the software. beta means simply not final, that means there can be various changes before the final release.
Posted Tue 03 Feb 09 @ 4:04 pm
rob.mccombe
I am a software developer and the beta windows releases are for developers to work on there sofware and drivers to get them ready for the final release of windows 7.
Yes there will be some changes to windows 7 but like i said before it will only be visual and gadget wise stuff that they will do and of course there will be stability updates before final release.
Why would microsoft bring out beta versions for developers then change stuff around so developers have to start all again thats not how it works im affraid.
Yes there will be some changes to windows 7 but like i said before it will only be visual and gadget wise stuff that they will do and of course there will be stability updates before final release.
Why would microsoft bring out beta versions for developers then change stuff around so developers have to start all again thats not how it works im affraid.
Posted Tue 03 Feb 09 @ 8:29 pm
metroplex2005
rob.mccombe wrote :
I am a software developer and the beta windows releases are for developers to work on there sofware and drivers to get them ready for the final release of windows 7.
a beta testing is not for software developers like you to do "work" on a software. microsoft self will do enough work on it. a beta release is a good way to find out some main bugs and problems with different hardware.
rob.mccombe wrote :
Yes there will be some changes to windows 7 but like i said before it will only be visual and gadget wise stuff that they will do and of course there will be stability updates before final release.
Why would microsoft bring out beta versions for developers then change stuff around so developers have to start all again thats not how it works im affraid.
Yes there will be some changes to windows 7 but like i said before it will only be visual and gadget wise stuff that they will do and of course there will be stability updates before final release.
Why would microsoft bring out beta versions for developers then change stuff around so developers have to start all again thats not how it works im affraid.
if you where a respectablly software developer, you wouldn´t tell such a nonsense. in fact, you are not part of the development team from microsoft windows 7, so you can only belive that there will be only changes in visuals and gadget wise stuff.
you know nothing about bugs and problems with special hardware, drivers or something else, you not own or tested by yourself. so eventually there ist something extreme buggy and they will change it. so the final version can be different in various ways to the beta version.
let me repeat: you know nothing about what they will change for the final release.
a respectablly software developer would say something like "with the beta version of windows 7, vjd works really good and stable. lets hope that the final version will do the same wonderful performance like the beta" or something in that way. that´s respectablly. what you say is only speculation.
Posted Wed 04 Feb 09 @ 11:49 am
Sonido Alto Voltaje
If you are really curious about windows 7 and future changes listen to these: http://www.winsupersite.com/paul/podcast.asp
Beta
'Beta' is a nickname for software which has passed the alpha testing stage of development and has been released to users for software testing before its official release. Beta testing allows the software to undergo usability testing with users who provide feedback, so that any malfunctions these users find in the software can be reported to the developers and fixed. Beta software can be unstable and could cause crashes or data loss.
A 'beta version' is the first version released outside the organization or community that develops the software, for the purpose of evaluation or real-world black/grey-box testing. The process of delivering a beta version to the users is called beta release. Beta level software generally includes all features, but may also include known issues and bugs of a less serious variety.
The users of a beta version are called beta testers. They are usually customers or prospective customers of the organization that develops the software. They receive the software for free or for a reduced price, but act as free testers.
Beta versions test the supportability of the product, the go-to-market messaging (while recruiting Beta customers), the manufacturability of the product, and the overall channel flow or channel reach.
Beta version software is likely to be useful for internal demonstrations and previews to select customers, but unstable and not yet ready for release. Some developers refer to this stage as a preview, a prototype, a technical preview (TP) or as an early access. As the second major stage in the release lifecycle, following the alpha stage, it is named after the Greek letter beta, the second letter in the Greek alphabet.
Often this stage begins when the developers announce a feature freeze on the product, indicating that no more feature requirements will be accepted for this version of the product. Only software issues, or bugs and unimplemented features will be addressed.
Developers release either a closed beta or an open beta; closed beta versions are released to a select group of individuals for a user test, while open betas are to a larger community group, usually the general public. The testers report any bugs that they found and sometimes minor features they would like to see in the final version.
An example of a major public beta test was when Microsoft started releasing regular windows Vista community technology previews (CTPs) to beta testers in January 2005. The first of these was build 5219. Subsequent CTPs introduced most of the planned features, as well as a number of changes to the user interface, based in large part on feedback from beta testers. windows Vista was deemed feature complete with the release of build 5308 CTP, released on February 22, 2006, and much of the remainder of work between that build and the final release of the product focused on stability, performance, application and driver compatibility, and documentation.
When a beta becomes available to the general public it is often widely used by the technologically savvy and those familiar with previous versions as though it were the finished product. Usually developers of freeware or open-source betas release them to the general public while proprietary betas go to a relatively small group of testers. Recipients of highly proprietary betas may have to sign a non-disclosure agreement. A release is called feature complete when the product team agrees that functional requirements of the system are met and no new features will be put into the release, but significant software bugs may still exist. Companies with a formal software process will tend to enter the beta period with a list of known bugs that must be fixed to exit the beta period, and some companies make this list available to customers and testers.
http://en.wikipedia.org/wiki/Software_release_life_cycle
Beta
'Beta' is a nickname for software which has passed the alpha testing stage of development and has been released to users for software testing before its official release. Beta testing allows the software to undergo usability testing with users who provide feedback, so that any malfunctions these users find in the software can be reported to the developers and fixed. Beta software can be unstable and could cause crashes or data loss.
A 'beta version' is the first version released outside the organization or community that develops the software, for the purpose of evaluation or real-world black/grey-box testing. The process of delivering a beta version to the users is called beta release. Beta level software generally includes all features, but may also include known issues and bugs of a less serious variety.
The users of a beta version are called beta testers. They are usually customers or prospective customers of the organization that develops the software. They receive the software for free or for a reduced price, but act as free testers.
Beta versions test the supportability of the product, the go-to-market messaging (while recruiting Beta customers), the manufacturability of the product, and the overall channel flow or channel reach.
Beta version software is likely to be useful for internal demonstrations and previews to select customers, but unstable and not yet ready for release. Some developers refer to this stage as a preview, a prototype, a technical preview (TP) or as an early access. As the second major stage in the release lifecycle, following the alpha stage, it is named after the Greek letter beta, the second letter in the Greek alphabet.
Often this stage begins when the developers announce a feature freeze on the product, indicating that no more feature requirements will be accepted for this version of the product. Only software issues, or bugs and unimplemented features will be addressed.
Developers release either a closed beta or an open beta; closed beta versions are released to a select group of individuals for a user test, while open betas are to a larger community group, usually the general public. The testers report any bugs that they found and sometimes minor features they would like to see in the final version.
An example of a major public beta test was when Microsoft started releasing regular windows Vista community technology previews (CTPs) to beta testers in January 2005. The first of these was build 5219. Subsequent CTPs introduced most of the planned features, as well as a number of changes to the user interface, based in large part on feedback from beta testers. windows Vista was deemed feature complete with the release of build 5308 CTP, released on February 22, 2006, and much of the remainder of work between that build and the final release of the product focused on stability, performance, application and driver compatibility, and documentation.
When a beta becomes available to the general public it is often widely used by the technologically savvy and those familiar with previous versions as though it were the finished product. Usually developers of freeware or open-source betas release them to the general public while proprietary betas go to a relatively small group of testers. Recipients of highly proprietary betas may have to sign a non-disclosure agreement. A release is called feature complete when the product team agrees that functional requirements of the system are met and no new features will be put into the release, but significant software bugs may still exist. Companies with a formal software process will tend to enter the beta period with a list of known bugs that must be fixed to exit the beta period, and some companies make this list available to customers and testers.
http://en.wikipedia.org/wiki/Software_release_life_cycle
Posted Thu 05 Feb 09 @ 1:12 pm
djreventon2007
why does that guy so angry? Is he jealous that the other guy knows just a little something about windows 7? what gives with all the hating?
Posted Fri 24 Apr 09 @ 11:22 pm