PureBasic Forums - English

NoahPhense, the code doesn't copile with PB4.0.

; Structure CLSID
; Data1.l
; Data2.w
; Data3.w
; Data4.b[8]
; EndStructure

IsNameChar() is declared as an array but gives an error

If you re-read my post, I don't claim that it works.

But if you want to read up on things. Here's the original link:
http://www.purebasic.fr/english/viewtop ... rmsdk+help

I'm going to work on it for a bit right now. I'll see what I come up with.

- np

NoahPhense wrote:If you re-read my post, I don't claim that it works.

[...]

I'm going to work on it for a bit right now. I'll see what I come up with.

- np

I don't blame you

I found a quite simple, yet effective solution for everyone who got the MS Platform SDK for Windows Server 2003 SP1 installed but don't get it working with PB. Basicaly you just need an alternative help browser as the default 'dexplore.exe'. Follow these steps:

1.) Download "H2 Viewer": http://helpware.net/mshelp2/h2viewer.htm
2.) Open PB and goto "Tools/Configure Tools..."
3.) Add a new tool with the following details:

- Commandline: Drive Root + Programm Root + \H2Viewer.exe
- Arguments: MS.PSDKSVR2003SP1.1033 /index %WORD
- Name: H2 Viewer (PSDKSVR2003)
- Shortcut: F1 *

Confirm twice if ya' done that :roll:

4.) Create a new source file and enter "CreateWindowEx_()"
5.) Place cursor over it and press F1. BOOM!

* In order to use the F1 shortcut you must remove it first from PB's default menu:

1.) Goto "File/Preferences..."
2.) Click on "General/Shortcuts"
3.) Scroll down to "Help -> Help..." and select it
4.) Select *BLANK* item from combobox and press "Set"
5.) Confirm of course...

In fact you could make the default 'dexplore.exe' work again with this method, problem is that it is limited in it commandline options. Anyway, I hope this helps for a while.

That's kewl.. I will try that out. But I will probably make it Alt-F1.


But just to make things more complicated.. I did try japbe .. and it went
straight to my SDK..?

Maybe we should look at the source of japbe.

- np

SimpleMind wrote:The only help I can get working is Kale's version. It's better than nothing but e.g. getsockname_() is only present in the 2003 SDK and not in the older version.

Ok, I do not know why it worked under my old system and/or older version of PB.

Maybe Fred knows a solution, always Fred, where would we be without this man?

getsockname()? who names their socks? sounds like a mental problem!



jk.... but really...

> To PB: that was also for me also the case in the past. But now I cannot get
> the same situation. Even when I push F1 the first time after a new start of
> PureBasic the PB help will not pop up.

Weird. Works for me. I even double-checked and yes, I'm using the same
version (Windows Server 2003 SP1 SDK). I don't have a "Help" folder for
PureBasic v4.00, if that makes any difference?

hmm :roll: workes here too and i do have a 'Help' folder, i just renamed 'Win32.hlp' to 'Win_32.hlp'
and in the 'Win32.cnt' i changed the first line to
:Base win_32.HLP

Best Henrik

Fluid Byte wrote:I found a quite simple, yet effective solution for everyone who got the MS Platform SDK for Windows Server 2003 SP1 installed but don't get it working with PB. Basicaly you just need an alternative help browser as the default 'dexplore.exe'. Follow these steps:

1.) Download "H2 Viewer": http://helpware.net/mshelp2/h2viewer.htm
2.) Open PB and goto "Tools/Configure Tools..."
3.) Add a new tool with the following details:

- Commandline: Drive Root + Programm Root + \H2Viewer.exe
- Arguments: MS.PSDKSVR2003SP1.1033 /index %WORD
- Name: H2 Viewer (PSDKSVR2003)
- Shortcut: F1 *

Confirm twice if ya' done that :roll:

awesome..

Thanks man.. this made my day.

- np

Here's the readme file I made for myself for the SDK; maybe it helps?

Finally, I got it working and this is what I've done:

- I deinstalled the Microsoft 2003 Server SDK R2
- Installed the Microsoft 2003 Server SDK SP1 by internet install.

I started the SDK first and ran PB40, pushed F1 on a API function. It worked.

Even when the SDK is not started first PB will start it now and even when there is a help folder present it works. The help folder contains the MVCOM helpfile and that works too.

The difference between the two installations is SP1 notation and R2 notation and the internet internet installation. The R2 version is downloaded in chunks put on disk and installed later from disk. The last install was an installation from internet.

Regards,

Marcel

> I started the SDK first and ran PB40, pushed F1 on a API function. It worked.
> Even when the SDK is not started first PB will start it

Yep, just like I said. You need to do that initial launch of the SDK for PureBasic
to "recognize" it in future -- without needing to launch the SDK in future.

PB wrote:Yep, just like I said. You need to do that initial launch of the SDK for PureBasic
to "recognize" it in future -- without needing to launch the SDK in future.

@PB, I think that besides your information given, there is a difference in installation when done by Internet install or local harddisk install by setup.exe and downloading the 25MB chunks. The R2 or SP1 version can also be part of the problem. Now I used the SP1.

After this experience I recommend the SP1 internet install and your startup information.

@All, Thanks for all help!

No, the types of installs have nothing to do with it.

And using the SP1, over R2 would just be a wrong thing to do.

I have R2 installed and I'll use it by just launching it and going to it
normally. I do have TWO win32 help files in the Help folder.

One is 24.2 mb's that's the older win32 api reference book, I have it
named WIN32_2.HLP, the other is the newer API help, it's 19.5mb's and
I have it named WIN32.HLP. Those work fine for my quick reference
within PB. If I need more, I use the platform SDK R2. And probably
the reason things are different for me, is because I'm running the new
IE7.

Anyhow, it's all good. Since I started tooling with japbe.. the R2 works
perfect inside of it.

- np

NoahPhense wrote:No, the types of installs have nothing to do with it.

Maybe, maybe not. If not than all problems around it would lead back to the first start of the SDK before PB is started. My mistake!

And using the SP1, over R2 would just be a wrong thing to do.

I looked what I miss and decided that the stuff is so special I would never use it and therefore don't miss it.

I have R2 installed and I'll use it by just launching it and going to it
normally. I do have TWO win32 help files in the Help folder.

How did you install SDK R2, webinstall or download and run the setup.exe.

One is 24.2 mb's that's the older win32 api reference book, I have it
named WIN32_2.HLP, the other is the newer API help, it's 19.5mb's and
I have it named WIN32.HLP. Those work fine for my quick reference
within PB. If I need more, I use the platform SDK R2.

How do you overcome the problem of selecting the proper HLP file? I use always the SKD.

And probably the reason things are different for me, is because I'm running the new IE7.

I can't use IE7 due to compatibility problems with Netilla VPN.

Anyhow, it's all good. Since I started tooling with japbe.. the R2 works perfect inside of it.

- np

Maybe it was due to my MS Visual Studio 2005 installation. The strange thing is that behind all the .NET information it every time has a link to "See xxxx in the Platform SDK". And again that is another source and not accessable to PB. That means also that I have tons of redundance information but not accessable in one way.


Great!