CLD-R Exam 2, Questions 38 and 39

[Ahmed.TUN]

Dear All,

Could you please help me with these two questions:

- Regarding the question 38, the vi that reads the binary files has the count input unwired on read binary file function, which is by default 1, isn't it? So I expected that on each iteration the function will return the first byte of the file which is 0, so answer D, While A is stated as the correct answer.

 For question 39, different operating systems is a requirement, however the asnwer that is reported true is A which uses Get System Directory VI which works under Windows only!

[Ahmed.TUN]

Dear All,

Could you please help me with these two questions:

- Regarding the question 38, the vi that reads the binary files has the count input unwired on read binary file function, which is by default 1, isn't it? So I expected that on each iteration the function will return the first byte of the file which is 0, so answer D, While A is stated as the correct answer.

 For question 39, different operating systems is a requirement, however the asnwer that is reported true is A which uses Get System Directory VI which works under Windows only!

[RavensFan · Accepted solution]

#38.  It is A.  You don't close the file, so the file pointer moves along with each read so you can get the next 1 byte in turn.  But actually it isn't one byte.  It is one element of whatever datatype you defined.  So if that constant is a U32, then you'd get a single U32 number, which consists of 4 bytes.

#39.  I would say A.  That uses the Get System Directory subVI to return a valid path to the user's documents, which should be freely writable by the logged in user unless their IT department really screwed them over and completely locked down the PC.

B and C are to paths that are very likely locked down to ordinary users unless they have admin rights.

D may not even be called by that exact path name because the literal path to the documents directories varies among different versions of Windows.  Are you sure that it only works in Windows?  Nothing in the detailed help of that subVI explicitly states that.  And I only use Windows, so I don't know how it would behave on a Mac.  It is very possible that if it only runs on Windows, the question was written in a way that the author may not have been thinking about non-microsoft OSes.  The fact of the matter is that MS Windows rules the world.  Sorry Mac dudes. 

[Ahmed.TUN]

Thank you so mch for your quick feedback RavensFan.

It's clear now regarding 38. It's a streaming from disk scenario

Regarding 39, It's true what you've said regarding B and C but A would work only in windows, that's why regarding the requirements I think it should be excluded and C will be the most modular choice

[RavensFan]

Are you sure it will only work in Windows?  (Check my last message, as I edited it and you may not have seen the added sentences.)

I can guarantee that the answer is not C.  It does not work on my PC.    "Documents and Settings" goes back to either Win7 or WinXP days.  On my Win 10 PC, that path doesn't exist.  It is C:\Users\MyUsername\Documents.  Or since answer C is showing for AllUsers, it is C:\Users\Public\Documents.

[aptivo]

39: The answer should be c, because of:

a) Get Sytem Directory -> not available for RealTime

b) If built and used in run-time, VI may points to path inside EXE file

c) correct

d) only available for Windows

[crossrulz]

---

@aptivo wrote:

39: The answer should be c, because of:

---

I am trying to remember all of the restrictions I ran into with saving things to the C:\Programs folder on a PC.  I want to say I ran into issues trying to save data to that folder.  Therefore I started saving my data to Public Documents (assuming Windows here).  I will have to experiment again to get my history refreshed.

[aptivo]

If building an installer you can select in the Source File Settings the folder attribute unlock for the containing folder where you'd like to install your application. All containing files and folders shall be write/modifiable.

[Ahmed.TUN]

---

@RavensFan wrote:

Are you sure it will only work in Windows?  (Check my last message, as I edited it and you may not have seen the added sentences.)

I can guarantee that the answer is not C.  It does not work on my PC.    "Documents and Settings" goes back to either Win7 or WinXP days.  On my Win 10 PC, that path doesn't exist.  It is C:\Users\MyUsername\Documents.  Or since answer C is showing for AllUsers, it is C:\Users\Public\Documents.

---

Honestly, I didn't try it in Linux or Mac, but that what was mentioned in LabVIEW Core 2 : It works only in Windows

[crossrulz]

---

@Ahmed.TUN wrote:

---

@RavensFan wrote:

Are you sure it will only work in Windows?  (Check my last message, as I edited it and you may not have seen the added sentences.)

I can guarantee that the answer is not C.  It does not work on my PC.    "Documents and Settings" goes back to either Win7 or WinXP days.  On my Win 10 PC, that path doesn't exist.  It is C:\Users\MyUsername\Documents.  Or since answer C is showing for AllUsers, it is C:\Users\Public\Documents.

---

Honestly, I didn't try it in Linux or Mac, but that what was mentioned in LabVIEW Core 2 : It works only in Windows

---

The Help says it won't work on RealTime.  So I left to assume it will work on Mac and Linux desktop.