Omega Owners Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

Welcome to OOF

Pages: 1 [2] 3  All   Go Down

Author Topic: windows 7..  (Read 1898 times)

0 Members and 1 Guest are viewing this topic.

cem_devecioglu

  • Guest
Re: windows 7..
« Reply #15 on: 13 October 2009, 20:56:24 »

Quote
Quote
Quote
I can't get Visual Studio 6 to work properly under it, even in XP compatibility mode.  It seems to corrupt filenames of source files  :'(

I also had problems opening the project first .. but I found the reason to be IDE exe has to be given admin rights..

looking from the net I see they dont support some ocx components.. but those are rarely used I think..
Yeah, needs a few tweaks to get it to go, but can't get around this corruption of source filenames,

Tend to run XP in a VM now when I need to modify old code

 I hope at least your final exe will work ..  microsoft teams promise for that..

tomorrow I will try direct port output codes like barcode writers..
Logged

TheBoy

  • Administrator
  • *****
  • Offline Offline
  • Gender: Male
  • Brackley, Northants
  • Posts: 107048
  • I Like Lockdown
    • Whatever Starts
    • View Profile
Re: windows 7..
« Reply #16 on: 13 October 2009, 20:59:05 »

Quote
Quote
Quote
Quote
and I must add also, it was not necessary to supply a driver for scsi card or any other thing for install..
Just because the OS provides a default driver, it doesn't automatically follow that it is the best one for the job.

you may be right KillerWatt..But havent seen any component working slower , may be later I will catch..
My old SB Live didn't work any slower when it first encountered the XP driver, the only problem was that half the features didn't work properly until the SB driver was installed.
And in true creative style, features knobbled with subsequent driver 'enhancements' ;D

Yes, I agree though, put on the correct drivers. Most devices don't have Win7 drivers, though normally Vista ones work. The MS ones aren't bad as a starting point, as they are the HCL approved ones submitted about 18 months ago in most cases.  Tends to be vga drivers that are updated very regularly
Logged
Grumpy old man

TheBoy

  • Administrator
  • *****
  • Offline Offline
  • Gender: Male
  • Brackley, Northants
  • Posts: 107048
  • I Like Lockdown
    • Whatever Starts
    • View Profile
Re: windows 7..
« Reply #17 on: 13 October 2009, 21:00:17 »

Quote
Quote
Quote
Quote
I can't get Visual Studio 6 to work properly under it, even in XP compatibility mode.  It seems to corrupt filenames of source files  :'(

I also had problems opening the project first .. but I found the reason to be IDE exe has to be given admin rights..

looking from the net I see they dont support some ocx components.. but those are rarely used I think..
Yeah, needs a few tweaks to get it to go, but can't get around this corruption of source filenames,

Tend to run XP in a VM now when I need to modify old code

 I hope at least your final exe will work ..  microsoft teams promise for that..

tomorrow I will try direct port output codes like barcode writers..
The say the compiled app will probably work (depending on ocx and environment), not that you can compile the app.
Logged
Grumpy old man

KillerWatt

  • Guest
Re: windows 7..
« Reply #18 on: 13 October 2009, 21:01:10 »

Quote
And in true creative style, features knobbled with subsequent driver 'enhancements' ;D
I don't try to fix things that ain't broke  ;)
Logged

cem_devecioglu

  • Guest
Re: windows 7..
« Reply #19 on: 13 October 2009, 21:02:53 »

Quote
Quote
Quote
Quote
Quote
I can't get Visual Studio 6 to work properly under it, even in XP compatibility mode.  It seems to corrupt filenames of source files  :'(

I also had problems opening the project first .. but I found the reason to be IDE exe has to be given admin rights..

looking from the net I see they dont support some ocx components.. but those are rarely used I think..
Yeah, needs a few tweaks to get it to go, but can't get around this corruption of source filenames,

Tend to run XP in a VM now when I need to modify old code

 I hope at least your final exe will work ..  microsoft teams promise for that..

tomorrow I will try direct port output codes like barcode writers..
The say the compiled app will probably work (depending on ocx and environment), not that you can compile the app.

Today, I could compile and I'm very happy for that..

And I think you can also.. but you need some free time..
Logged

TheBoy

  • Administrator
  • *****
  • Offline Offline
  • Gender: Male
  • Brackley, Northants
  • Posts: 107048
  • I Like Lockdown
    • Whatever Starts
    • View Profile
Re: windows 7..
« Reply #20 on: 13 October 2009, 21:06:20 »

Quote
Quote
Quote
Quote
Quote
Quote
I can't get Visual Studio 6 to work properly under it, even in XP compatibility mode.  It seems to corrupt filenames of source files  :'(

I also had problems opening the project first .. but I found the reason to be IDE exe has to be given admin rights..

looking from the net I see they dont support some ocx components.. but those are rarely used I think..
Yeah, needs a few tweaks to get it to go, but can't get around this corruption of source filenames,

Tend to run XP in a VM now when I need to modify old code

 I hope at least your final exe will work ..  microsoft teams promise for that..

tomorrow I will try direct port output codes like barcode writers..
The say the compiled app will probably work (depending on ocx and environment), not that you can compile the app.

Today, I could compile and I'm very happy for that..

And I think you can also.. but you need some free time..
I can compile, my problem is if I save the source after I've modified it, it corrupts filenames.

Maybe I could find a solution, but time is something I don't have  :'(
Logged
Grumpy old man

cem_devecioglu

  • Guest
Re: windows 7..
« Reply #21 on: 13 October 2009, 21:09:55 »

Quote
Quote
Quote
Quote
Quote
Quote
Quote
I can't get Visual Studio 6 to work properly under it, even in XP compatibility mode.  It seems to corrupt filenames of source files  :'(

I also had problems opening the project first .. but I found the reason to be IDE exe has to be given admin rights..

looking from the net I see they dont support some ocx components.. but those are rarely used I think..
Yeah, needs a few tweaks to get it to go, but can't get around this corruption of source filenames,

Tend to run XP in a VM now when I need to modify old code

 I hope at least your final exe will work ..  microsoft teams promise for that..

tomorrow I will try direct port output codes like barcode writers..
The say the compiled app will probably work (depending on ocx and environment), not that you can compile the app.

Today, I could compile and I'm very happy for that..

And I think you can also.. but you need some free time..
I can compile, my problem is if I save the source after I've modified it, it corrupts filenames.

Maybe I could find a solution, but time is something I don't have  :'(

is win7 working under vm ?
Logged

TheBoy

  • Administrator
  • *****
  • Offline Offline
  • Gender: Male
  • Brackley, Northants
  • Posts: 107048
  • I Like Lockdown
    • Whatever Starts
    • View Profile
Re: windows 7..
« Reply #22 on: 13 October 2009, 21:17:35 »

Quote
Quote
Quote
Quote
Quote
Quote
Quote
Quote
I can't get Visual Studio 6 to work properly under it, even in XP compatibility mode.  It seems to corrupt filenames of source files  :'(

I also had problems opening the project first .. but I found the reason to be IDE exe has to be given admin rights..

looking from the net I see they dont support some ocx components.. but those are rarely used I think..
Yeah, needs a few tweaks to get it to go, but can't get around this corruption of source filenames,

Tend to run XP in a VM now when I need to modify old code

 I hope at least your final exe will work ..  microsoft teams promise for that..

tomorrow I will try direct port output codes like barcode writers..
The say the compiled app will probably work (depending on ocx and environment), not that you can compile the app.

Today, I could compile and I'm very happy for that..

And I think you can also.. but you need some free time..
I can compile, my problem is if I save the source after I've modified it, it corrupts filenames.

Maybe I could find a solution, but time is something I don't have  :'(

is win7 working under vm ?
This is directly on my desktop, but I can replicate on one of my VMs as well.
Logged
Grumpy old man

cem_devecioglu

  • Guest
Re: windows 7..
« Reply #23 on: 13 October 2009, 21:19:14 »

Quote
Quote
Quote
Quote
Quote
Quote
Quote
Quote
Quote
I can't get Visual Studio 6 to work properly under it, even in XP compatibility mode.  It seems to corrupt filenames of source files  :'(

I also had problems opening the project first .. but I found the reason to be IDE exe has to be given admin rights..

looking from the net I see they dont support some ocx components.. but those are rarely used I think..
Yeah, needs a few tweaks to get it to go, but can't get around this corruption of source filenames,

Tend to run XP in a VM now when I need to modify old code

 I hope at least your final exe will work ..  microsoft teams promise for that..

tomorrow I will try direct port output codes like barcode writers..
The say the compiled app will probably work (depending on ocx and environment), not that you can compile the app.

Today, I could compile and I'm very happy for that..

And I think you can also.. but you need some free time..
I can compile, my problem is if I save the source after I've modified it, it corrupts filenames.

Maybe I could find a solution, but time is something I don't have  :'(

is win7 working under vm ?
This is directly on my desktop, but I can replicate on one of my VMs as well.

hmmm.. my solutions finished.. ;D


Logged

HolyCount

  • Guest
Re: windows 7..
« Reply #24 on: 13 October 2009, 22:39:25 »

Hmmm -- all greek to me -- but it's taken me yonks to sort out bl**dy Vista .... not sure yet if I can bring myself to put the 7 upgrade in the drive .... knowing my luck everything will go t*ts up !
Logged

Lazydocker

  • Omega Queen
  • *****
  • Offline Offline
  • Gender: Male
  • Woodbridge, Suffolk
  • Posts: 18848
  • Constantly Bullied by a certain Admin
    • View Profile
Re: windows 7..
« Reply #25 on: 13 October 2009, 22:52:54 »

Quote
Quote
Quote
Quote
Quote
and I must add also, it was not necessary to supply a driver for scsi card or any other thing for install..
Just because the OS provides a default driver, it doesn't automatically follow that it is the best one for the job.

you may be right KillerWatt..But havent seen any component working slower , may be later I will catch..
My old SB Live didn't work any slower when it first encountered the XP driver, the only problem was that half the features didn't work properly until the SB driver was installed.
And in true creative style, features knobbled with subsequent driver 'enhancements' ;D

Yes, I agree though, put on the correct drivers. Most devices don't have Win7 drivers, though normally Vista ones work. The MS ones aren't bad as a starting point, as they are the HCL approved ones submitted about 18 months ago in most cases.  Tends to be vga drivers that are updated very regularly

I was led to believe this is because Win 7 is actually win 6.x, a completely re-worked Vista  :-/ :-/ Basically because of the problems they had with the release of Vista, they didn't want to go through it again
Logged
Whatever it is... I didn't do it

cem_devecioglu

  • Guest
Re: windows 7..
« Reply #26 on: 14 October 2009, 09:31:35 »

Quote
Hmmm -- all greek to me -- but it's taken me yonks to sort out bl**dy Vista .... not sure yet if I can bring myself to put the 7 upgrade in the drive .... knowing my luck everything will go t*ts up !

dont be pessimistic.. even the earlier version dont ask for any driver and dont make any problem..simply install from cd and start work.. And I'm not talking about an ordinary pc.. it was a workstation from HP with Adaptec SCSI and a 15K RPM SCSI hard drive and a specific mobo.. I remember how much effort I spend when installing XP on it.. :y
Logged

KillerWatt

  • Guest
Re: windows 7..
« Reply #27 on: 14 October 2009, 19:32:27 »

Quote
Hmmm -- all greek to me -- but it's taken me yonks to sort out bl**dy Vista .... not sure yet if I can bring myself to put the 7 upgrade in the drive .... knowing my luck everything will go t*ts up !
NEVER upgrade
Logged

TheBoy

  • Administrator
  • *****
  • Offline Offline
  • Gender: Male
  • Brackley, Northants
  • Posts: 107048
  • I Like Lockdown
    • Whatever Starts
    • View Profile
Re: windows 7..
« Reply #28 on: 14 October 2009, 20:09:51 »

Quote
Quote
Quote
Quote
Quote
Quote
and I must add also, it was not necessary to supply a driver for scsi card or any other thing for install..
Just because the OS provides a default driver, it doesn't automatically follow that it is the best one for the job.

you may be right KillerWatt..But havent seen any component working slower , may be later I will catch..
My old SB Live didn't work any slower when it first encountered the XP driver, the only problem was that half the features didn't work properly until the SB driver was installed.
And in true creative style, features knobbled with subsequent driver 'enhancements' ;D

Yes, I agree though, put on the correct drivers. Most devices don't have Win7 drivers, though normally Vista ones work. The MS ones aren't bad as a starting point, as they are the HCL approved ones submitted about 18 months ago in most cases.  Tends to be vga drivers that are updated very regularly

I was led to believe this is because Win 7 is actually win 6.x, a completely re-worked Vista  :-/ :-/ Basically because of the problems they had with the release of Vista, they didn't want to go through it again
Win7 is, confusingly, Windows 6.1.  So, yes, a (significantly) improved/tweaked Vista.

XP (Windows 5.1) was really a tweaked (and bodged in places) Windows 2000 (Windows 5.0), and was flawed in a number of ways, and suffered due to poor quality drivers.

Microsoft had to go through the pain of some significant changes with Vista, and at the same time implemented more thoroughly that previously a signed driver policy (driver has to be certified) in an effort to improve the crap splatted out by cheap chinese hardware manufacturers.


If software obeyed the long stated Windows programming rules, for the most part they worked fine under Vista (some architectural changes needed in drivers though).  That software that didn't obey the rules often didn't run so well.  Vista was in Beta for long enough for developers to fix issues, but many didn't bother.  And the inevitable happened, and everyone said it was all Microsoft's fault.
Logged
Grumpy old man

STMO999

  • Guest
Re: windows 7..
« Reply #29 on: 14 October 2009, 20:14:06 »

I dont pretend to understand all this stuff but, for the vast majority of home users like myself, who dont do anything more than forums and online banking and stuff, any old OS will do really ;D
Logged
Pages: 1 [2] 3  All   Go Up
 

Page created in 0.016 seconds with 16 queries.